Creating a "bad" file with a given MD5 is, by design, an extremely difficult task. Since an MD5 hash is 128 bits, one would have to create somewhere on the order of 2^^127 random files to have even odds of coming up with one with a given hash. This is computationally impossible.
Then again, there are believed to be some weaknesses in MD5, making this a little bit easier.
As RAM stores data with capacitors, it loses its contents within a few refresh periods. For example, 150ns RAM would lose its contents entirely in <450ns. VRAM and processor caches are usually even faster. No way you're going to recover anything from THAT...
An Apple representative on Apple's discussion board posted, in a thread discussing the $HOME and/tmp bugs, that "Safari Update 1-10-03 addresses the issue or issues being discussed in this and other forums."
The 'defiant holdout' you're thinking of was Giles Corey, who was suspected of being a witch (er, wizard) in the Salem witch trials in 1692. The story goes that instead of either pleading guilty (which would have him killed for being a witch) or pleading innocent (which would have him killed for lying --- evidence from the accused was counted as untrustworthy), both of which would have left his property to others, he instead was 'pressed' to death, which allowed his descendants to keep his property.
Well, I'm still a student at the Menlo School, which is a pretty good school. Among other things, it offers a server for student use: thibs. Shell access, virtually unlimited web and file sharing space --- it's great. Beat that!
Slashdot Mirror
You're right, I meant infeasible, or practically impossible.
Or you can use Apple's quartzwm, which makes X windows behave exactly like Mac windows because they *are*.
Then again, there are believed to be some weaknesses in MD5, making this a little bit easier.
As RAM stores data with capacitors, it loses its contents within a few refresh periods. For example, 150ns RAM would lose its contents entirely in <450ns. VRAM and processor caches are usually even faster. No way you're going to recover anything from THAT...
The post's here.
(This comment posted with Safari)
Correction: I have a copy that I bought, new, at my local bookstore.
Well, read this. Among other things, the coffee was somewhere around 180 or 190 degrees F. Yeow!
It's still in print. I've got a copy.
A neat story.
*smirk*
However, even better is to use large packages of advertising material as free fuel. Better than firewood, and cheaper too!
I bet three e-quatloos on it being five minutes.
Well, I'm still a student at the Menlo School, which is a pretty good school. Among other things, it offers a server for student use: thibs. Shell access, virtually unlimited web and file sharing space --- it's great. Beat that!
The source (yes, nasm input == source) to my entry is available here.
Link. Apparently Tesla may also have come up with something like radar in WW1 as well. Very strange.
Note that this does not prevent you from `broadcasting an IP address'; it just protects (?) you from attacks.
No, I'm not telling you how I did it. [grin] Figure it out on your own. Or improve on my attempt. Whichever.
Just tell me if you improve on it.
No, I didn't try *that* hard on this project.
The catch? I did it in 5,038 bytes, including a nifty color icon.
Beat that.
Try PPP.menu (available from Network.prefpane). You don't need Internet\ Connect.app for ANYTHING.
Or Xenix.
Airframe, by Michael Crichton.
How about YOU?
Distributing source without a makefile won't work. Makefiles are easy to put together.