So Mr. Katz, now that you can be considered a Jock, does that mean we don't have to read anymore whiny articles about high-school geek-trouncing? Thank the Lord Almighty! --
Uh, for everyone's information, Internet2 is going to give them exactly what they're looking for... And get this, it's being developed by academics! Holy pocket protector, Batman, the nerds are helping the corps! --
Fine, I stand correct on #1. But the problem was fixed in version 7.0, which is normal is software development, so there's no reason to get M$oft bash-happy.
BUT, number do is definitely correct:
Murchie said the bug was a minor problem in Microsoft's instructions for using the software and has been resolved. "It was not a product flaw. Only under circumstances (where) the site (had) no password could anybody get to it," he said. "If normal policies were in place, there's no impact."
There was no bug in the software, just in the "instructions for using the software" and if you're like me, instructions for software use don't usually tell the whole story. In fact Microsoft's documentation for its software is a hell of a lot better than most open source docs I've seen. --
Let's do some fact checking here before blindly bashing Microsoft!
1) The bug was in the CUSTOM SOFTWARE that the Russians were running against the database.
3) The security "flaw" in the newer version that they upgraded to was only there if NO PASSWORD WAS SET. Well, of course there's going to be a security issue if you don't set your passwords!
It's about time Slashdot took some time to actually READ the stories they post. --
Slashdot Mirror
Um, nope.
--
So Mr. Katz, now that you can be considered a Jock, does that mean we don't have to read anymore whiny articles about high-school geek-trouncing? Thank the Lord Almighty!
--
Uh, for everyone's information, Internet2 is going to give them exactly what they're looking for... And get this, it's being developed by academics! Holy pocket protector, Batman, the nerds are helping the corps!
--
BUT, number do is definitely correct:
Murchie said the bug was a minor problem in Microsoft's instructions for using the software and has been resolved. "It was not a product flaw. Only under circumstances (where) the site (had) no password could anybody get to it," he said. "If normal policies were in place, there's no impact."
There was no bug in the software, just in the "instructions for using the software" and if you're like me, instructions for software use don't usually tell the whole story. In fact Microsoft's documentation for its software is a hell of a lot better than most open source docs I've seen.
--
1) The bug was in the CUSTOM SOFTWARE that the Russians were running against the database.
3) The security "flaw" in the newer version that they upgraded to was only there if NO PASSWORD WAS SET. Well, of course there's going to be a security issue if you don't set your passwords!
It's about time Slashdot took some time to actually READ the stories they post.
--