4 ms·

It’s a very common MacBook M1. I agree that most developers use an interpreter or a compiler with the default settings. At least on the mac everything seems to

It’s a very common MacBook M1. I agree that most developers use an interpreter or a compiler with the default settings. At least on the mac everything seems to target a very recent instructions set. But it’s quite common to see hot paths being optimised using not so old instructions on amd64 too. I also agree that you should keep most of your users happy. How many users are using such old hardware and software? At work, we disabled old TLS versions and many cipher suites for security reasons because we knew no one would care. We kept TLSv1.2 enabled because we still had users using software incompatible with TLSv1.3 unfortunately.

vkaku 3y ago
I hear you, I hear you. ARM is at least 30 years old, if not more :) My first computer (in school days) was a 6502 based BBC Micro - so, maybe half an ARM (and a leg) computer. I am well aware of the TLS/SSL issues, I was personally responsible for large scale patching of these ciphers at a large retailer for a very large fleet of machines on their datacenters. DM me if you want to know the details. Yet, Today - I am the one slamming this practice for web servers serving system and firmware updates, and I write about how Debian solves this problem well (in another thread on this HN page). It is okay to upgrade people to forward looking infrastructure, and the cost of not keeping sustainability is steep. The correct way to get people to TLS v1.3 is to allow some means by which people can get the updates needed for both algorithms, as well as the new certificates. And the deal is that TLS v1.3 may not be enough for a post quantum world. This may be the right time to undo our mistakes of the past.