Re:Ask PG: Make the login form available over HTTPS only?
by brudgers on Monday July 23, 2012 @12:38PM
(#4281826)
This thread has gotten me thinking about how PG might approach security. The existence of https on the site is a starting point.
It allows anyone who is serious about a secure channel to create one while not advertising the fact that some people might find security necessary on a "news" site. Yes, it's security by obscurity, which of course shouldn't be used as the primary method but it probably reduces the attractive nuisance.
But if PG was going to code something up, he wouldn't advertise the fact, nor his approach. It would instead be along the lines of "Lisp as a secret weapon."
And it certainly wouldn't be something based on "industry best practices."
If pg spent 2 hours downloading the libraries for and hooking into the API of, say, bcrypt or pbkdf2, that on top of the rest of his authentication code would result in a benefit once the password database has been stolen. There is a man-in-the-middle possibility because HTTP is still a valid login method, though you could argue he can spend less time securing his code against a database breach.
If pg spent 1 hour making SSL the only option for logins, the resulting benefit is that all communication of the password is secure, though you could argue he now has to spend much more time securing his code against a database breach.
Of course, if he spent 3 hours doing both, everything is more secure. But we don't always have time to spend.