6 ms·
Probably one of these two: 1)HN is a side project for a busy man, and SSL/HTTPS simply isn't very high on the feature list. 2) Arc, the language HN is written
by mixmax 16y ago
Probably one of these two:
1)HN is a side project for a busy man, and SSL/HTTPS simply isn't very high on the feature list.
2) Arc, the language HN is written in, doesn't support SSL/HTTPS
- burgerbrain 16y agoIf you can't do it properly...
- nuclear_eclipse 16y agoIt's open source, you could always donate some of your own time to do it properly...
- mike-cardwell 16y agoAs jbyers said, it should be trivial to stick a webserver which supports SSL in front of the app. Perhaps it would be a good idea to modify the app to add the secure flag to the cookie it sets though.
- chopsueyar 16y agoWhy do you care? I've already used Firesheep three times to downvote using your account. I'll do it with this comment, too.
- mike-cardwell 16y agoCool, so what's your password then? Seeing as it doesn't matter if anyone finds it out...
- chopsueyar 16y agoI only care about your session. You can keep your password, unless I brute-force it from a 37signals webapp.
- mike-cardwell 16y agoAh, so you do care enough to not share your password. So I guess the reason I care about SSL is the same reason you care about SSL.
- jbyers 16y agoIt should be straightforward to put HN behind an SSL proxy (nginx, apache, stunnel, what-have-you) if the application constructs URLs properly. HN seems to, but in some applications that's a big "if". I'd be happy to test and supply an nginx 0.8 configuration if that would help.