Last year I disabled TLS 1.0/1.1 on my personal server and encountered problems. Turns out Mono (Keepass2Android) and Qt (QBittorrent) libraries on Android for some reason had not enabled higher-than-TLS-1.0 support, although AFAIK they supported it at the time.
So yeah, I ended up reenabling TLS 1.0/1.1 on a system on which I had full control over the clients connecting to it. Given the difficulty and nature of current attacks, I figured the low risks to me personally weren't worth the inconvenience.
I commend the Debian project for making the push for this, but I wonder if the world is ready to be TLS 1.2+ only.
Comments
Last year I disabled TLS 1.0/1.1 on my personal server and encountered problems. Turns out Mono (Keepass2Android) and Qt (QBittorrent) libraries on Android for some reason had not enabled higher-than-TLS-1.0 support, although AFAIK they supported it at the time.
So yeah, I ended up reenabling TLS 1.0/1.1 on a system on which I had full control over the clients connecting to it. Given the difficulty and nature of current attacks, I figured the low risks to me personally weren't worth the inconvenience.
I commend the Debian project for making the push for this, but I wonder if the world is ready to be TLS 1.2+ only.