News for hackers. Stuff that matters.

A comment on Chromium and Mozilla to enforce 1 year validity for TLS certificates. Parent comment

Re:Chromium and Mozilla to enforce 1 year validity for TLS c... by cutler on Sunday June 28, 2020 @12:27PM (#23669884)
Guess what - not all websites are businesses. In fact not all websites are dynamically-generated so why the fsck do we all have to put up with this madness? Make HTTPS/SSL necessary for transactional sites but for simple static sites give me a break.
[ Parent | on HN ]
Re:Chromium and Mozilla to enforce 1 year validity for TLS c... by riffic on Sunday June 28, 2020 @12:50PM (#23670090)
did you know there are ISPs out there that inject garbage code into the html of unprotected sites?

get out of here with this HTTPS is unnecessary tedium.

[ Parent | on HN ]
Re:Chromium and Mozilla to enforce 1 year validity for TLS c... by gsich on Sunday June 28, 2020 @04:55PM (#23671975)
Better not do business with shady companies then.
[ Parent | on HN ]
Re:Chromium and Mozilla to enforce 1 year validity for TLS c... by riffic on Sunday June 28, 2020 @05:30PM (#23672217)
or you could follow established best practices and secure your site with TLS.
[ Parent | on HN ]
Re:Chromium and Mozilla to enforce 1 year validity for TLS c... by gsich on Sunday June 28, 2020 @07:08PM (#23672761)
Both. I am not responsible if you chose a shitty ISP.
[ Parent | on HN ]
Re:Chromium and Mozilla to enforce 1 year validity for TLS c... by Spivak on Sunday June 28, 2020 @09:44PM (#23673607)
But this makes no sense because the user has basically zero control of how their traffic is routed to/from you.

If we could trust the entire network we wouldn’t need TLS for any site.

[ Parent | on HN ]