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
-
Our site is coming soon. It will be one of the best ever! I know so. Brian and Penny -
Well we found out they have a good hash decryption+ salt solution, which many companies would buyagentGFY *at* gmail.comComment
-
-
Bumparooni for crack.agentGFY *at* gmail.comComment
-
2 fiddy for hash decryption + salt solution!
going once.agentGFY *at* gmail.comComment
-
nobody got hackedComment
-
We don't know that.
But we do know there is an epic groundbreaking solution for hash decryption + salt!!!agentGFY *at* gmail.comComment
-
So basically what we discovered is that if you're using crakrevenue your passwords are stored in plain text? Copy.Comment
-
This went on the ignore list quick by crakagentGFY *at* gmail.comComment
-
Another bump for perfect "hash decryption + salt" solution!agentGFY *at* gmail.comComment
-
Busy for a bump, not busy for a great solution!agentGFY *at* gmail.comComment
-
Hi + salt hereagentGFY *at* gmail.comComment
-
Another day, another great solutionagentGFY *at* gmail.comComment
-
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 + saltComment
-
automatic exchange - paxum , bitcoin,pm, payza
. daizzzy signbucks caution will black-hat black-hat your traffic
ignored forever :zuzana designsComment
-
i don't know why they have limitations on password length anywayComment
-
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?Comment
-
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.agentGFY *at* gmail.comComment
Comment