3 ms·
Ask HN: What TLS clients do you need to support?
The Let's Encrypt CA is looking at the question of what TLS protocol and ciphersuite defaults to offer sysadmins by default when they turn on HTTPS on their web servers. (Of course, if you use Let's Encrypt you can configure your servers with any cryptography of your choice; you don't have to use the defaults.)
A topic that's been in the news a lot is the way that old TLS clients require protocols or cryptography that's now known or believed to have vulnerabilities (like SSLv3, RC4, Diffie-Hellman with 1024-bit primes...).
This can pose a dilemma for server administrators because they want to support older clients, but don't want to support insecure cryptography. The TLS ciphersuite negotiation features give admins some flexibility about this, but not always a way to avoid undesirable tradeoffs.
If you run an HTTPS site or other TLS service, what are the oldest clients that you consider it essential to support for your particular service? I'm particularly curious about MSIE and Java clients, but any other compatibility requirements would be interesting too.