Look at the security of email. There's lots of so-so proposals to help control spam, but there's no big win anywhere.
Networked computers depend on communication. Pretty any communication can be used to circumvent security. And there's all the people you can exploit, too. All you can you is make the lock as good as you can, but no lock will be perfect.
One more feature of floppies is that it's not too costly to give them away. Maybe USB keys will come down in price, but they won't stack up very well.
Your ISP server could also be another floppy killer, but ISPs don't want you to use their space, so they make it inconvenient (more inconvenient than floppies) to upload and download files.
The specific result is that it's much easier than random chance to generate two strings with the same MD5 value. This implies that MD5 is much less secure than previously assumed.
No, it's not an algorithm that will efficiently find a string with the same MD5 value as your program A, but it's a significant step in that direction. MD5 is now known to have enough of a flaw that it is reasonable to assume that it's only a matter of time and ingenuity to exploit it.
Does this mean/. will hold off on changing this horrid color scheme until it's determined that nothing bad will happen? Like being able to read titles and links?
I agree that this color scheme is unhealthy and dangerous, especially to young children. Torturing memory card is exactly the opposite, except for the occasional injestion of electronic parts.
Would someone please DNS attack this color scheme?
on
Network Attacks Via DNS
·
· Score: -1, Offtopic
DNS cool, but it's doubtful security sucks, and so does this color scheme.
While DNS insecurity exists, would someone please use it to change this color scheme?
Yes, I know about changing it. to whatever., but working around a bad UI is even worse than working around bad security.
Slashdot Mirror
... and hide the key!
Because it's Utnubu spelled backwards.
Oh yeah, there was Sitefinder. Never mind.
Networked computers depend on communication. Pretty any communication can be used to circumvent security. And there's all the people you can exploit, too. All you can you is make the lock as good as you can, but no lock will be perfect.
I mainly use Linux, but 12% reboots for XP seems far too high. Maybe they should differentiate machines loaded with spyware and those that aren't.
Your ISP server could also be another floppy killer, but ISPs don't want you to use their space, so they make it inconvenient (more inconvenient than floppies) to upload and download files.
No, it's not an algorithm that will efficiently find a string with the same MD5 value as your program A, but it's a significant step in that direction. MD5 is now known to have enough of a flaw that it is reasonable to assume that it's only a matter of time and ingenuity to exploit it.
It's because /. is cutting costs by outsourcing their headlines. You could already tell that it started with the color schemes.
Well, at least you can write off a little bit of the loss each year. It's around $5K or so. Of course, you aren't going to get your interest back.
When is MS going to fix this bug with unreadable colors? And why is it that it always happens on /.?
... uses light colors on a white background to help users stay squinted and confused.
This bug is in Mozilla, too!
Now I understand why /. has this horrible color scheme.
Does this mean /. will hold off on changing this horrid color scheme until it's determined that nothing bad will happen? Like being able to read titles and links?
If Microsoft can release this service pack, then surely there is hope that /. can change this horrid color scheme.
Niether iz speling
Your opinion might be different, but to me, it's a close call.
I agree that this color scheme is unhealthy and dangerous, especially to young children. Torturing memory card is exactly the opposite, except for the occasional injestion of electronic parts.
While DNS insecurity exists, would someone please use it to change this color scheme?
Yes, I know about changing it. to whatever., but working around a bad UI is even worse than working around bad security.
Or maybe this color scheme is a /. joke that I don't get.
There's no way to avoid a lot of manual testing, except at /. where they can implement an awful color scheme with next-to-zero testing, apparently.
Mozilla and Firebox are cool, but spoofing sucks, 5-year old bugs suck, and so does this color scheme.
Maybe we can direct IBM's research toward self-healing color schemes.
Maybe one of these graphics wizards can help /. out. We can only hope.
Microsoft sucks, outsourcing sucks, and so does this color scheme.