Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Simply banning any kind of legacy protocol is not exactly in good spirit. People should have freedom of choice when it comes to running THEIR OWN infrastructure.


The ban is just for .gov sites.

"This proposed initiative, “The HTTPS-Only Standard,” would require the use of HTTPS on all publicly accessible Federal websites and web services."


I don't think anyone was trying to tell you how to build your core application network or your home LAN. SSL Everywhere is about critical connections subject to interception.


I was referring to public networks as well. I should be able to do HTTP GET to my server if I choose to do so. In the same way as I can open a socket to my server and write plain text to it.


I think you should be able, in the sense that it should not be legally or technologically prohibited nor prohibitive. I do think there is a line, beyond which a service should be obligated to encrypt everything, and that line is somewhere around carrying others' messages, certainly around getting common carrier status for the same.

Edit: I must stress, social not legal consequences should apply. I'm in no hurry to invite government scrutiny of this line.




Consider applying for YC's Summer 2026 batch! Applications are open till May 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: