Hashes.com Automated Paid Recovery Escrow - Now Live!

[Plum]

I'm somewhat confused by what "maximum cracks needed" means. If I put 2 hashes in a list at $10 per hash, should I set the maximum for 2 if I'm willing to escrow the amount for both? It defaults to 1.

Yes, if you want both cracked and can escrow the amount you would set the maximum for 2.

 

[Hashes]

I'm somewhat confused by what "maximum cracks needed" means. If I put 2 hashes in a list at $10 per hash, should I set the maximum for 2 if I'm willing to escrow the amount for both? It defaults to 1.

Say you have 1,000 hashes. You price them @ 10$/hash.

You would need to deposit 10k to escrow to be able to post the list.

But if you set maximum number of cracks to 10. Then you only need 100$ in escrow to post your list.

 

[gpuhash_me]

You are not clear about fees. 5% escrow fee and 0.0005BTC withdrawal fee, right?

 

[Hashes]

You are not clear about fees. 5% escrow fee and 0.0005BTC withdrawal fee, right?

Correct.

 

[sunip99]

what format to upload the found ?
just password
or
hash:passsword ?

 

[Cyclone]

what format to upload the found ?
just password
or
hash:passsword ?

hash:password

Also make sure correct algorithm is selected from dropdown menu (see attached upload_found.png).

 

[techtrip]

@Hashes, are you going to be collecting the passwords found from hashes.com?

 

[techtrip]

@Hashes, are you going to be collecting the passwords found from hashes.com?

Should be keeping them & releasing as a wordlist. Separate from hashkiller list,

I would, as a way to gain more trust

 

[capric0rnu$]

@Hashes, are you going to be collecting the passwords found from hashes.com?

not good idea.Especially in paid section.

Very often people need privacy of found passwords
Didn't you see posts?
Do not post in public

Crackers also have secrets

 

[techtrip]

@Hashes, are you going to be collecting the passwords found from hashes.com?

not good idea.Especially in paid section.

Very often people need privacy of found passwords
Didn't you see posts?
Do not post in public

Crackers also have secrets

I didn't assume he was going to share hash:plain. Just the password.

Crackers have secrets? Does that make everyone better at it? Or just the person with the most secrets?

I think you've spent so much time cracking "in secret" that you forgot about the community.

 

[Hashes]

@Hashes, are you going to be collecting the passwords found from hashes.com?

not good idea.Especially in paid section.

Very often people need privacy of found passwords
Didn't you see posts?
Do not post in public

Crackers also have secrets

I didn't assume he was going to share hash:plain. Just the password.

Crackers have secrets? Does that make everyone better at it? Or just the person with the most secrets?

I think you've spent so much time cracking "in secret" that you forgot about the community.

No I won't be collecting the finds from paid section and sharing the plaintexts. For free list management sure. Paid no. Often in paid there is a lot of work that are put into the finds. Leaking those wouldn't be fair to the crackers.


However I will be putting together a dict from my own collections for the site, and to be shared among the community. Full cross-referenced / de-duped against other public dicts, such as Hashkiller / Hashes.org.

 

[capric0rnu$]

@Hashes, are you going to be collecting the passwords found from hashes.com?

not good idea.Especially in paid section.

Very often people need privacy of found passwords
Didn't you see posts?
Do not post in public

Crackers also have secrets

I didn't assume he was going to share hash:plain. Just the password.

Crackers have secrets? Does that make everyone better at it? Or just the person with the most secrets?

I think you've spent so much time cracking "in secret" that you forgot about the community.

No I won't be collecting the finds from paid section and sharing the plaintexts. For free list management sure. Paid no. Often in paid there is a lot of work that are put into the finds. Leaking those wouldn't be fair to the crackers.


However I will be putting together a dict from my own collections for the site, and to be shared among the community. Full cross-referenced / de-duped against other public dicts, such as Hashkiller / Hashes.org.

I fail to see how it's unfair to the crackers. They found it. They got paid for it. We put ALOT of effort in for the WPA's in the free section, Days sometimes but always share the results. I must be missing something that may be obvious to others?

ask gpuhash to share wordlists from gpuhash.me

 

[Hashes]

@Hashes, are you going to be collecting the passwords found from hashes.com?

not good idea.Especially in paid section.

Very often people need privacy of found passwords
Didn't you see posts?
Do not post in public

Crackers also have secrets

I didn't assume he was going to share hash:plain. Just the password.

Crackers have secrets? Does that make everyone better at it? Or just the person with the most secrets?

I think you've spent so much time cracking "in secret" that you forgot about the community.

No I won't be collecting the finds from paid section and sharing the plaintexts. For free list management sure. Paid no. Often in paid there is a lot of work that are put into the finds. Leaking those wouldn't be fair to the crackers.


However I will be putting together a dict from my own collections for the site, and to be shared among the community. Full cross-referenced / de-duped against other public dicts, such as Hashkiller / Hashes.org.

I fail to see how it's unfair to the crackers. They found it. They got paid for it. We put ALOT of effort in for the WPA's in the free section, Days sometimes but always share the results. I must be missing something that may be obvious to others?

When you are running hashes. Example... Say on hashes.org.

You know what you are submitting will be going to the public for everyone to see.
When you are running hashes on hashes.com escrow. You are running hashes for pay, in private.

It would be different if say in the TOS I stated "All hashes cracked hashes plaintext will be harvested and shared to the public in the form of {Hashes.com Dict}

Often when more "Elite" crackers, run hashes for the public they are not using their more private, custom developed dicts for a reason as they don't want those passwords to be given away for free. Thus the reason they only use for them for paid work.

 

[Hashes]

@Hashes, are you going to be collecting the passwords found from hashes.com?

not good idea.Especially in paid section.

Very often people need privacy of found passwords
Didn't you see posts?
Do not post in public

Crackers also have secrets

I didn't assume he was going to share hash:plain. Just the password.

Crackers have secrets? Does that make everyone better at it? Or just the person with the most secrets?

I think you've spent so much time cracking "in secret" that you forgot about the community.

No I won't be collecting the finds from paid section and sharing the plaintexts. For free list management sure. Paid no. Often in paid there is a lot of work that are put into the finds. Leaking those wouldn't be fair to the crackers.


However I will be putting together a dict from my own collections for the site, and to be shared among the community. Full cross-referenced / de-duped against other public dicts, such as Hashkiller / Hashes.org.

I fail to see how it's unfair to the crackers. They found it. They got paid for it. We put ALOT of effort in for the WPA's in the free section, Days sometimes but always share the results. I must be missing something that may be obvious to others?

When you are running hashes. Example... Say on hashes.org.

You know what you are submitting will be going to the public for everyone to see.
When you are running hashes on hashes.com escrow. You are running hashes for pay, in private.

It would be different if say in the TOS I stated "All hashes cracked hashes plaintext will be harvested and shared to the public in the form of {Hashes.com Dict}
Often when more "Elite" crackers, run hashes for the public they are not using their more private, custom developed dicts for a reason as they don't want those passwords to be given away for free. Thus the reason they only use for them for paid work.

 

[techtrip]

So you collect fees for posting and cracking. Then collect the passwords for your private use and turn around and make more money?

No wonder you bought hashkiller.co.uk :)

 

[Hashes]

@Hashes, are you going to be collecting the passwords found from hashes.com?

not good idea.Especially in paid section.

Very often people need privacy of found passwords
Didn't you see posts?
Do not post in public

Crackers also have secrets

I didn't assume he was going to share hash:plain. Just the password.

Crackers have secrets? Does that make everyone better at it? Or just the person with the most secrets?

I think you've spent so much time cracking "in secret" that you forgot about the community.

No I won't be collecting the finds from paid section and sharing the plaintexts. For free list management sure. Paid no. Often in paid there is a lot of work that are put into the finds. Leaking those wouldn't be fair to the crackers.


However I will be putting together a dict from my own collections for the site, and to be shared among the community. Full cross-referenced / de-duped against other public dicts, such as Hashkiller / Hashes.org.

I fail to see how it's unfair to the crackers. They found it. They got paid for it. We put ALOT of effort in for the WPA's in the free section, Days sometimes but always share the results. I must be missing something that may be obvious to others?

When you are running hashes. Example... Say on hashes.org.

You know what you are submitting will be going to the public for everyone to see.
When you are running hashes on hashes.com escrow. You are running hashes for pay, in private.

It would be different if say in the TOS I stated "All hashes cracked hashes plaintext will be harvested and shared to the public in the form of {Hashes.com Dict}

Often when more "Elite" crackers, run hashes for the public they are not using their more private, custom developed dicts for a reason as they don't want those passwords to be given away for free. Thus the reason they only use for them for paid work.

What happened to sharing in the community :) :)

I stated above I will be releasing a "hashes.com dict" which will be a custom built dict of my own wordlists. Designed to be highly effective and efficient at the same time. Sorted by frequency. 1.5gb in size. All genuine passwords.

I clearly am biased in saying this. But it will be more effective than any public dict out there.

 

[Hashes]

So you collect fees for posting and cracking. Then collect the passwords for your private use and turn around and make more money?

No wonder you bought hashkiller.co.uk :)

The hashes/passwords from escrow are not harvested nor will they be input into the hash lookup database that will be soon be released.

 

[techtrip]

So you collect fees for posting and cracking. Then collect the passwords for your private use and turn around and make more money?

No wonder you bought hashkiller.co.uk :)

The hashes/passwords from escrow are not harvested nor will they be input into the hash lookup database that will be soon be released.

Sorry. I misunderstood you.

 

[Reconsniper]

Bravo Hashes,
Please bring on the goodness of your password list, it will be very well appreciated and devoured by all :) Your words are music to my ears!!!! Playing such a sweet symphony, that makes my heart skip a beat! Lol
Tally Ho!!!

 

[sillva]

Most definitely biased lol. But to be fair. I would expect a list from you to be a most valuable addition to anyone's collection

Really enjoyed this amusing remark, followed by a sincere one
+rep