I'd be willing to bet very few people use truly unique passwords across all their accounts. While personal responsibility is paramount, human nature is what it is, and (again, imo) all sites that require authentication should do it well (over SSL).
Therefore, I doubt that PG would rely on it as a primary means of preventing mischief on HN.
Post intelligent comments under my name?
Cost me a few karma points by trolling?
Other than the ability to downvote and change the topline color, it's no different from yours. It's not the karma points which make an HN'ers posts better, it's the relevance of their participation.
But regardless of how one slices and dices it, my HN account does not contain sensitive information and the consequences of a security breech of my account are trivial. HN is not Wells Fargo.
After reading the grandparent comment about wanting my karma I changed my password for the first time since joining. But rest assured, the old password demonstrated how low value access to my HN login is.
It's foolish to introduce security where none is required, and even more foolish to introduce the overhead of a security apparatus which doesn't meaningfully increase security.
To put it another way, if PG emails me directly using the private address, I'll see it eventually. But I will probably see anything sent to the public address more quickly...though again probably not right away.
Just as I don't see security on HN as high importance, for me, emails related to it are not treated as time critical. However, separating them out from my normal inbox makes anything coming from HN stand out.
I think this is only a reasonable consideration when the implementation is inconvenient. We're talking about an SSL login on a site that already uses HTTPS. This is not a particularly difficult endeavour.
I'd add that using SSL for the sake of using SSL may give HN'ers a false impression regarding the priority given to securing communications on the news site.
HN does not have a private messaging system (at least at my karma level) and the bottom line is that my communications are being published to the internet at large. It is difficult to see what purpose security serves.
HSTS, as we've seen here recently, cuts down the risk significantly, especially if HN were to submit itself to browser preloaded lists.
Could someone please explain to me how this could happen ? By my understanding, that is exactly the type of attack that SSL was designed to protect against.
The real-time commercial value of a person's actual posts to HN is even less, i.e. any man in the middle who is manipulating HN comments is doing so at the expense of forgoing more profitable opportunities.
The root of the security issue is using open wireless networks, and these are vulnerable to man in the middle exploit even when SSL is used.