throw new ArgumentException (String, String, Exception)
Hmmm. I'd have guessed at "open sesame".
or "guest"
http://www.youtube.com/watch?v=UduILWi2p6s
On a forum I ran many years ago, I did a database search and it was astonishing how many people used "password" as their password. And "open sesame" ran it a fairly close second. Mind you, that's a trivial forum, not a head of state's email account (allegedly).
Nope. They were stored as MD5 hashes. But if you MD5 "password" and do a database search on that value, you got a list of hits. And by the way, I didn't write the software, or determine how it stored passwords, or have any control over how it did it. It was a commercial product.
I did think that might have been what you'd have done, but there was the niggling doubt mind....
Single MD5, un-salted? Amazing how many people think "job done"...
throw new ArgumentException (String, String, Exception)
You didn't salt your hash?
Must be back in the day, anything less than a salted SHA256 is considered insecure by many techies I know as it's easier (especially in asp.net) to hash with md5/sha1 instead of taking the effort to build a hashing system for sha256/512 that can incorporate a salt.
TheAnimus: We picked up a project for a large legal client, all their clientel passwords were stored in plain text, banking details too, it was a sony scale fail (the excuse from the previous dev was that it was not externally facing...)
I didn't pepper or vinegar it, either.
As I said earlier ....
1) It was "many years ago"
2) I didn't have any control over how commercial software stored it's passwords.
The software did it how the software did it, and that was that. I didn't write the stuff. I just used it.
There are currently 1 users browsing this thread. (0 members and 1 guests)