3 ms·
> But if your [computer’s CPU][0] is so slow that a modern TLS negotiation would take so long as to be unusable The author is actually pretty explicit that the
by shakna 6y ago
> But if your [computer’s CPU][0] is so slow that a modern TLS negotiation would take so long as to be unusable
The author is actually pretty explicit that they're talking about a System 6 Mac, which has all the hardware necessary not to be too slow for TLS. It's just that it's so old that finding a working SSL library for it is difficult, which on some fronts I can sympathise with...
But SSL should still be a requirement to prevent your users from having crap injected by whoever the hell is between you and them.
[0] https://jcs.org/system6c https://jcs.org/system6c
- anthk 6y ago> System 6 Mac, which has all the hardware necessary not to be too slow for TLS. Eh, maybe not CPU wise, but 4MB of RAM are a bit shortish.
- shakna 6y agoAmigaOS manages it with 512Kb of RAM.
- anthk 6y agoI know Amiga has modern SSL libraries, but with just 512kb of RAM to run iBrowse? Sure? I tried to emulate some m68k macs, and definitely, as the PC, 8MB are the minimum enough (with paging) to browse without issues with an old Netscape release, or icab. PC's have it easier because a stripped Minix2 with Lynx and some light SSL library could do that with ease on a high 486/Pentium and 4MB of RAM. One day I'll compile a modern Dillo with mbedtls for a virtual 486 with 4-8MB under Qemu.