Heya peeps,
I just made a .2 version of a distributed password cracking program called CrackAtHome. It's an open source project so if anyone wants to get on board and help me code it up to more uber I'd appeciate the help.
The new version has a gui and can now do attacks on ftp and pop3 in addition to the original ssh. Check it out at crackathome.com
Since its not testing the passwords locally,(it's not doing shadowed passwords like john the ripper etc...) its targeting remote servers, the bottleneck isn't program speed but network latency.
Technically its not brute force, its a dictionary attack.
Java is very quick to develop distributed computing programs in.
A distributed approach to remote password cracking has a couple of advantages, multiple computers divides up the network latency bottleneck, plus more ip's is less suspicious and harder to write rules to block.
But it's more of an experiement, I don't really know if it will be an effective attack. I figure in the worst case it will work as a ddos cause it will force the target to disable the account under attack.
Name:
Anonymous2007-10-28 5:31
Uh... this is why any sysop that's not totally retarded sets up rules that filter incoming connections after repeated failed login attempts.
Also, SecurID.
Name:
Anonymous2007-10-28 5:36
>>1
You can tune a file system, but you can't tune a fish.
Name:
Anonymous2007-10-28 7:22
Warning: A forced joke meme detected. Proceed with caution
Name:
Anonymous2007-10-28 15:38
>>4
In most situations the bottleneck won't be network latency, it'll be the authentication attempt on the remote computer.
All the same, this is a stupid concept.