4 ms·
On the other side, it is now almost impossible to use the internet on a retro computer. I absolutely understand the drive to use more secure TLS, but it's a re
by timw4mail 6y ago
On the other side, it is now almost impossible to use the internet on a retro computer.
I absolutely understand the drive to use more secure TLS, but it's a really sad experience to see that you can load Google, but have nearly every link unable to load.
It wasn't that long ago that I could try out some ancient browser on some modern website, and at least see it fail to render well. Now you can't even connect.
This leads to interesting situations with, say, PowerPC Mac software sites. Either they have http connections, or they use user-agent sniffing to downgrade TLS.
- mrunkel 6y ago> This leads to interesting situations with, say, PowerPC Mac software sites. Either they have http connections, or they use user-agent sniffing to downgrade TLS That doesn't work. The user-agent is passed after the encryption channel is established. What they do is offer all the options, and the client picks the best one they can support. However, why would this need to be HTTPS to begin with? If you're not transmitting anything private, HTTP works just fine.
- toast0 6y agoDowngrading TLS only works so far, a lot of older clients won't understand SHA-256 signatures on modern certs. I don't think anybody will do SHA-1 certs anymore, so you would need to give those users a self-signed certificate or something.