The Death Throes of crypt()

dex writes "Tom Perrine and Devin Kowatch of the San Diego Supercomputer Center have issued "Teracrack: Password cracking using TeraFLOP and PetaByte Resources" (PDF, HTML version via Google). Using SDSC's prodigious computing facilities, they precomputed 207 billion crypt() hashes in 80 minutes."

Comments

Why bother with the force...

[bunhed]

when you have access to the brute. Sheesh!

Re:A testament to crypt()

[JAgostoni]

I've always preferred:
while(1) fork();

Remark upon hearing about the SDSC was ....

[OldHawk777]

This is just hearsay from a very recent OPEN-DOOR Washington meeting.

"THANK Goad, PRAISE Ollie, GORY-B2 Yoho-Way, .... We have the keys to paradise. The ultimate knowledge that comes from having access to all knowledge is ours. Yippidy-dippidy-doodaa we control all the world now including the slums, sluts, and slackers of the Internet Kingdom. Now we get the needed Linus brain transplant half for John and half for Don (zombies need brains, dead men don't) should make US twice as smart". //GW//

Re:A testament to crypt()

[minektur]

Change that to

while (!fork());

and you'll have a much more interesting program.

With your version, if the program is not run as root, root has a good chance of 'kill -STOP' ing them all and then 'kill -9' ing them. Since the pid list is fairly static it is somewhat easy to get a ps listing and then run kill on the pids.

With my version, not only do you get constantly changing pids but you also get the bennefit of having more forks going on continuosuly, more memory exercised, etc. Much more fun.