5 ms·
I wish unencrypted HTTP/2 without TLS could be supported in major browsers. Although use of encryption should be very strongly encouraged, making it mandatory c
by dheera 11y ago
I wish unencrypted HTTP/2 without TLS could be supported in major browsers. Although use of encryption should be very strongly encouraged, making it mandatory creates a lot of headaches in certain scenarios.
- finnn 11y agoSuch as?
- Aldo_MX 11y agoGenerating a trusted certificate?
- dheera 11y agoBrowsers shouldn't be the internet police. If either server or client wants to use encryption, encryption should be used. The browser should not have a say in this decision. Examples of cases where unencrypted HTTP makes sense: * Public, non-sensitive content that you need to distribute or broadcast using CDNs (such as Amazon's), who may charge you hundreds or thousands of dollars to install a custom server certificate if you want to use your own domain * Servers with limited CPU power and which are not serving sensitive content (e.g. embedded devices, Raspberry Pis, Arduinos et al.) * Getting a website up for $0.00 without paying some troll corporation to "validate" your certificate * Getting a website up to distribute information without revealing YOUR identity In any case, there are use cases, and it should not be the job of the browser to police this.
- finnn 11y ago> * Public, non-sensitive content that you need to distribute or broadcast using CDNs (such as Amazon's), who may charge you hundreds or thousands of dollars to install a custom server certificate if you want to use your own domain If TLS is mandatory, the price of this will have to go down > * Servers with limited CPU power and which are not serving sensitive content (e.g. embedded devices, Raspberry Pis, Arduinos et al.) I've served TLS off embedded devices like these no problem >* Getting a website up for $0.00 without paying some troll corporation to "validate" your certificate Certificates are free (WoSign, StartCom, LetsEncrypt) >* Getting a website up to distribute information without revealing YOUR identity None of the free CAs validate anything beyond your email address (StartCom demands an address, but they don't seem to do much beyond validate that it's a valid address). DV certs are not to validate identity, just that you are the domain owner
- ori_b 11y ago> I've served TLS off embedded devices like these no problem I doubt it -- Raspberry Pi is easy, but even HTTP on an Arduino would be a stretch.
- daurnimator 11y ago> > * Servers with limited CPU power and which are not serving sensitive content (e.g. embedded devices, Raspberry Pis, Arduinos et al.) > I've served TLS off embedded devices like these no problem On e.g. a esp8266 you can only have a single TLS connection at a time. While you can have hundreds of normal TCP sessions. > Certificates are free (WoSign, StartCom, LetsEncrypt) - WoSign doesn't work on mildy old devices - StartCom certs are expensive to revoke - LetsEncrypt doesn't exist yet
- bkeroack 11y agoJust because the CA system currently sucks (letsencrypt.org may help this) doesn't mean you should give up on crypto entirely.
- sp332 11y agoWhat if I have a bare IP address and don't feel like getting a domain name for it?
- IgorPartola 11y agoDon't know about you but I have a really hard time remembering those long 128 but addresses. A domain name is just so much easier.
- sp332 11y agoWell if you have a /64 (which is the recommended minimum), then you probably have the first 64 bits memorized before too long. After that you can get creative with ::dead:beef or whatever.
- deleted 11y ago[deleted]
- rektide 11y agoSuch as if you are ZeroConf networking with someone in the same area.
- viraptor 11y agoYou can get a certificate for an ip address.
- sp332 11y agoI couldn't find any info on this when I researched before, but I guess some CA's will do it and some won't. GlobalSign seems to.
- collinmanderson 11y agoI wish there was opportunistic encryption, or at least a system more similar to how ssh keys work.