This isn't an implementation bug, but i'd sure label it as a design bug.
How hard would it be to use an absolute clock - "stardate..." - on the shuttle, instead of our earthly dates that wrap once a year? Heck, the hours also wrap every day and there is no limitation that shuttles must not be out there between 23:59 and 00:01!
In a technology as advanced and as expensive as this one, the omission of a requirement for proper time handling, free from the "problems" we have down here, is definitely a bug.
I would think something as simple as a CRC or date check would be simple enough, once you download the content it shouldn't ever change so the CRC should always pass and the modified date should never change.
I bet the code that computes the CRC and date to send to the server will also be changed to send in the expected values.
You discover that your neighbours are using your unsecured wireless network without your permission.
This seems to suggest a scenario where it was not the owner's intention to have an open network, and at some point in time he discovers it's being used.
If we're talking about someone smart enough to play this trick on the neighbours, the network would likely be secure in the first place.
In a court: Attourney: Did you sleep with John? Witness: No, I didn't. Attourney: Did you sleep with Mark? Witness: No, I didn't. Attourney: Did you sleep with Nigel? Witness: I refuse to answer that question.
The difference with AT&T is that it's happening before any trial. But the conclusion is obviously the same.
"It could be tomorrow, but most likely it'll be 1,000, 10,000, 100,000 years from now," says Jeno Sokoloski.
This is one part of the timeframe - WHEN it will start.
The other one is - HOW LONG does it take? I mean, even if it starts tomorrow, the process might take 5000 years to complete.
Also, with many IE flaws (and the OS itself) being fixed, it probably becomes much easier picking up the "dormant" office app's and find the more flagrant flaws.
After a period of intense fixing on a component, one expects the remaining flaws to be harder to find - not that there aren't any, of course.
Maybe the computers get the updates not from Microsoft directly, but from a WSUS machine, which some administrator loads with the approved updates (not including WGA).
That might explain why:
- no client machines have WGA installed
- they don't need it in order to get other updates
Slashdot Mirror
About your signature, apparently tasers are one of the possibilities.
This isn't an implementation bug, but i'd sure label it as a design bug. ..." - on the shuttle, instead of our earthly dates that wrap once a year? Heck, the hours also wrap every day and there is no limitation that shuttles must not be out there between 23:59 and 00:01!
How hard would it be to use an absolute clock - "stardate
In a technology as advanced and as expensive as this one, the omission of a requirement for proper time handling, free from the "problems" we have down here, is definitely a bug.
I would think something as simple as a CRC or date check would be simple enough, once you download the content it shouldn't ever change so the CRC should always pass and the modified date should never change.
I bet the code that computes the CRC and date to send to the server will also be changed to send in the expected values.
Yes, it's easy to google for it, provided you already know that the solution relies in a key changer.
You discover that your neighbours are using your unsecured wireless network without your permission.
This seems to suggest a scenario where it was not the owner's intention to have an open network, and at some point in time he discovers it's being used.
If we're talking about someone smart enough to play this trick on the neighbours, the network would likely be secure in the first place.
In a court:
Attourney: Did you sleep with John?
Witness: No, I didn't.
Attourney: Did you sleep with Mark?
Witness: No, I didn't.
Attourney: Did you sleep with Nigel?
Witness: I refuse to answer that question.
The difference with AT&T is that it's happening before any trial. But the conclusion is obviously the same.
"It could be tomorrow, but most likely it'll be 1,000, 10,000, 100,000 years from now," says Jeno Sokoloski.
This is one part of the timeframe - WHEN it will start.
The other one is - HOW LONG does it take? I mean, even if it starts tomorrow, the process might take 5000 years to complete.
After a period of intense fixing on a component, one expects the remaining flaws to be harder to find - not that there aren't any, of course.
Boy, these guys don't seem to learn from their own mistakes. "Oooooh, 340 undecillion should be enough for everyone"
Let's hope that the complicated encryption keys are also secure ones.
Do you live in Europe and work in the US, perhaps?
640 days should be enough for everyone
Where's the link for the porn streamed from Europe?
It's the dreaded P bug once again.
That might explain why:
- no client machines have WGA installed
- they don't need it in order to get other updates
these very same guys were sueing p2p users for sharing their ebooks.
does it run Vista?
That L stands for lighting, right?
I wouldn't be surprised if Steven Seagal were giving a hand to this research.
The guys at Valve totally rock with their Stem technology.
They are already moving to the next step, testing it on humans.
Verifying someone's age online is easy.
The hard part is blocking Alt-X or Ctrl-Alt-X in a browser-independent manner.
was all belong to us!
Obviously.
The priority now is the rural areas, the penetration there is only 60%. And if you exclude the animals, I bet it is much lower than that.
Damn, the summary is too small. This time must actually RTFA before commenting.
Star$$$1 3/2137236
http://science.slashdot.org/article.pl?sid=06/06/