Reputation
Top tag
Next privilege 200 Rep.
See reduced ads
Badges
3
Impact
~933 people reached

  • 0 posts edited
  • 0 helpful flags
  • 0 votes cast
Sep
24
awarded  Autobiographer
Jul
16
comment Is it better to hash n*x times in sha1 or n times in sha512 on the client side?
This was originally done as a way to increase time required incase of a mitm so that it's not just plain text. The time required would be minimal but is still something. I'd love to have a native implementation of it in all browsers, but that's not likely to happen. The 1s is the maximum, and if they're using ie8 that's saddening.The other reason was to make sure that they cannot run away with other passwords. Since I think everyone should be doing this "community service." As it helps us all.
Jul
14
awarded  Citizen Patrol
Jul
13
comment Is it better to hash n*x times in sha1 or n times in sha512 on the client side?
The password is never seen. I don't know what you're talking about. The users password that they are giving to me is never seen. In the event of a databreach, the password is never seen and on top of it the time taken to get it is increase. They are broken, and pretty broken at that. Md5 is insanely broken, and thus I refuse to use it for anything. Sha1 is on its way to a full break, and thus I didn't really trust it. I do trust SSL but since they can say "I don't support encryption" a user could in theory, end up using a clear connection.
Jul
12
awarded  Student
Jul
12
asked Is it better to hash n*x times in sha1 or n times in sha512 on the client side?