3 ms·
In my mind, this is more of a problem with TLS than it is a problem with older, slower, or simpler computers. Encypted, complex, and/or fast-churning protocols
by RodgerTheGreat 4y ago
In my mind, this is more of a problem with TLS than it is a problem with older, slower, or simpler computers. Encypted, complex, and/or fast-churning protocols are sold as delivering security and efficiency, but in practice, for many applications, they primarily function as a ratchet to artificially induce obsolescence.
- robinsonb5 4y agoThis. I tried spinning up a Win2k VM a few months back and was surprised to find that the web's now basically off limits to Win2K because of TLS. What's even more surprising is that the same barrier doesn't keep an Amiga[1] off the web. (Javascript is another matter, of course!) [1] https://github.com/jens-maus/amissl https://github.com/jens-maus/amissl
- anthk 4y agoInstall Legacy Update and Retrozilla.
- robinsonb5 4y agoThanks, I'll check those out.
- rollcat 4y agoWell the alternatives are: to stay offline, proxy through a more powerful relay (e.g. with WireGuard, seems to be able to run on an ESP32, but that's just moving the problem around), or... convince the world that the most widely deployed encryption protocol needs radical change?
- NoGravitas 4y agoThe main practical solution seems to be to use a http-to-https proxy. Inspired by nostalgia and stuff retrocomputing people were doing on the fediverse, I recently spun up a MacOS 8.1 VM. Getting online basically took installing such a proxy on the host, since there's no browser with modern TLS that will run on a 68040 Mac.