Reply to thread

Message

<blockquote data-quote="Markshall" data-source="post: 365459" data-attributes="member: 1872">Let's face it, no one's perfect at anything so we've all made mistakes when coding, so what's your biggest mistake?Personally, my dumbest mistake was about about 5 years ago when I was developing a publicly released user system in PHP, basically what I did was set up my users table in phpMyAdmin and I had these 2 columns, one was 'password' and the other was 'password_un'. 'un' standing for 'unprotected' (lol.)Looking back, it's one of the stupidest things I've done. Why have a column for a hashed password, and a column for the un-hashed password. Reason being was that I wanted to be able to email users with the content of 'password_un' in their user record in the event of them forgetting their password.TL;DR: &quot;stored hashed and un-hashed passwords in database to be able to email users their un-hashed password when they forget it&quot;So what's yours?</blockquote>

[QUOTE="Markshall, post: 365459, member: 1872"] Let's face it, no one's perfect at anything so we've all made mistakes when coding, so what's your biggest mistake? Personally, my dumbest mistake was about about 5 years ago when I was developing a publicly released user system in PHP, basically what I did was set up my users table in phpMyAdmin and I had these 2 columns, one was 'password' and the other was 'password_un'. 'un' standing for 'unprotected' (lol.) Looking back, it's one of the stupidest things I've done. Why have a column for a hashed password, and a column for the un-hashed password. Reason being was that I wanted to be able to email users with the content of 'password_un' in their user record in the event of them forgetting their password. TL;DR: "stored hashed and un-hashed passwords in database to be able to email users their un-hashed password when they forget it" So what's yours? [/QUOTE]

Verification

Reply to thread

Connect with us

Newest members