Browsing shouldn't be affected as it doesn't use OpenSSL. However, I share your concerns. The target is the next stable (two years), but many of us are running unstable or testing.
Browsers use TLS, but I don't think many of them use OpenSSL's implementation. Firefox uses NSS, and Chrome uses BoringSSL (which is related but not affected by this change).
Comments
Browsing shouldn't be affected as it doesn't use OpenSSL. However, I share your concerns. The target is the next stable (two years), but many of us are running unstable or testing.
What are you talking about? Web servers AND web browsers both use OpenSSL. If it's disabled, you can't speak it at all in Debian.
Browsers use TLS, but I don't think many of them use OpenSSL's implementation. Firefox uses NSS, and Chrome uses BoringSSL (which is related but not affected by this change).