Salty Cracker - is a distributed, GPGPU-powered supercomputer. Right now it's main specialization is cryptanalysis. Unlike most of public distributed computation projects, you may submit your own tasks, instead of just contributing your CPU time & electricity bills. This is done via points system - you earn points() by helping others with their tasks, and then others will work on your one.

What is important to do now?

As our first run would be large bunch of unsalted MD5 hashes, it is important to collect all relevant hashes before we start. After we would start working on this set, it would be impossible to add any new hashes to the first working set. So it is important to inform everyone interested to submit their hashes here. That's where I need your help now

If you want to submit your hashes, you'll need to register or login on the forum, and then proceed to hash management page.

Understanding points system

1 point = 1 hour of computation at 1 trillion operations/second (benchmarked on MD5 algorithm). When submitting you task you might specify a priority. Task with highest priority is executed on a whole supercomputer. Task with priority=2 would "eat" twice more points than a regular one. Priority <1 is also possible.

Timeline:

Phase 1: starting to gather hashes, especially unsalted MD5. This will form first unsalted MD5 batch.

Phase 2: a little more distant near future - starting production run on submitted MD5 hashes

Security considerations

There are several security modes available:

If you mark your hashes as public - everyone would be able to query it's result in case of success. Also, they would be visible at "last recovered keys" page.

If you mark your hashes as private - only you would be able to see it. If anyone would submit exactly the same hash as public - it would become public. Please note, that unsalted private hashes are sent for brute forcing to everyone, so one would be able to salvage your key, if it would be cracked on his computer (but obviously would have no idea who is the owner and were should he use it).

Later 2 more modes would be available: local - your hashes are sent only to the clients you own, so the only security risk is 14.by server. And finally personal server when you would have your own server instance with full control.

Terms of use

By using this service you agree the following terms:

1) You are only allowed to submit hashes of your own forgotten passwords or other legal sources. Any operations with hashes from illegal sources are strongly prohibited, and might lead to account banning & removal of all associated data (including hashes and recovery results) without any notification.
2) You use this service on your own responsibility. "Salty cracker" administration is not liable for any damages or loses.
3) For every point you own "Salty cracker" administration may get 5% tax. Other than that "Salty cracker" administration have no advantages over regular users (i.e. same rules for tasks priority).
4) These terms are subject to change without notification.

Comment: Well, I might have hidden #3, but want to be honest with users from the very beginning. Personally I have no tasks for these 5%, so I suppose it would stay untouched.