Bug#865649: cups HTTPS issues -- Lack of SHA-2 certificate, weak TLSv1.0 crypto)

["of.the@protonmail.com" <of.the@protonmail.com>]

Was TLSv.1.0 already disabled back in July 2015 and this is a regression or is it time now to disable it permanently and completely in the default config? See below a prior changelog.

cups (2.1~b1-1)

  * New 2.1~b1 release

disable TLS/1.0 support.

-- Didier Raboud <odyx@debian.org>  Thu, 09 Jul 2015