Crickets.

Bump for new age hash decryption+salt! :)

Another bump for the great phrase:"hash decryption+salt" hahahahahahah

Hi. Can i buy your special hash decryption + salt algorithm? I'd resell to NSA if possible.

Bump for perfect "hash decryption + salt" solution!

E=MC with a little 2 above the C

hi eric do you have icq?

Imagine this, they are no longer responding :P

You could make a fortune on this guys. Sell the hash decryption+salt thing!

So were they hacked? Still not sure

Fiddy people who were not hacked but some thought they were so a thread was made and the votes were cast and the winner is....... YOU

Well we found out they have a good hash decryption+ salt solution, which many companies would buy

what is salt?

Bumparooni for crack.

2 fiddy for hash decryption + salt solution!

going once.

nobody got hacked

We don't know that.

But we do know there is an epic groundbreaking solution for hash decryption + salt!!!

So basically what we discovered is that if you're using crakrevenue your passwords are stored in plain text? Copy.

This went on the ignore list quick by crak

Another bump for perfect "hash decryption + salt" solution!

Busy for a bump, not busy for a great solution!

Hi + salt here

Another day, another great solution

Reminds me a little of my bank.

Password length must be 6 characters exactly, letters and numbers only.

A few years ago they changed from a standard web field to an "onscreen keyboard" that you have to click to enter the password. It only lets you enter upper case, but there were no problems with logging me in, even though my password (previously entered with the keyboard) was mixed case. If they were using hashes, there's no way that the uppercase version I entered would match the stored mixed case password. Wouldn't be unreasonable to guess they could be storing the pass in plain text format. Then again, maybe they have some o' dat special decryption algorithm + salt

:pimp:pimp

i don't know why they have limitations on password length anyway

Yes, this is possible, because even if the system uses hashes internally, you submit the password to the login page in cleartext. So it would certainly be possible for a program to do a once-off check and notify if it sees the password is too long.

Question is WHY is there the limit in the first place for crak? Password prompts can be made fixed size on a page - they'll just scroll sideways - and there's no real performance difference between sending 5 characters or 500 characters. So why are passwords limited to this length? Even if crak are encrypting them (special decryption algorithm + salt) that means they can be decrypted. Why would a program ever need to access your cleartext password?

:1orglaugh:1orglaugh:1orglaugh:1orglaugh:1orglaugh

:winkwink::winkwink::winkwink:

lol good thing u caught my post i tried to add to the post n somehow edited it out. doing too many things at once.

but yeah things that make you go hmm...

No. They just stored it without case. Banks have specific limitations, and yours were letters and numbers only, so they "threw" your pass through something of an regex that would check if the pass had any of those and either block it (if it had special chars) or lowercase/uppercase all letters that were initially input. Thats why not it doesnt matter what u enter.