TLS on Defender TD5https://td5.390er.de/kategorien/tls/Recent content in TLS on Defender TD5HugodeSun, 30 Aug 2026 13:12:34 +0200TLS 1.2 and 1.3 on System 7: a 68K client measured against a live serverhttps://td5.390er.de/68k-tls/tls-on-system-7-68k-client-measured/Sun, 30 Aug 2026 12:08:09 +0200https://td5.390er.de/68k-tls/tls-on-system-7-68k-client-measured/<h2 id="question">Question</h2> <p>No browser that runs on System 7 can open an <code>https://</code> URL against a server configured today: Netscape 3 and 4, iCab 2.9 and MacWeb speak SSL 2/3 with RC4 and DES, without SNI and without SHA-2 certificates, and every current server closes the handshake. The usual remedy is to terminate TLS on a proxy and hand the guest plain HTTP. This article asks the narrower question: can the guest itself complete a modern handshake, and at what cost in seconds?</p>