Since you managed to get this to work, I am closing this bug. Thanks!
** Changed in: cups (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1526999
Title:
cups
Aha! I think it is that for some weird reason, a SHA-384 certificate may
be the cause of this problem. I changed my server certificate to SHA-1
and TLS 1.2 works again. (and CUPS uses GnuTLS, so my OpenSSL cannot be
the problem)
--
You received this bug notification because you are a member of
** Changed in: cups (Ubuntu)
Status: Invalid => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1526999
Title:
cups is intolerant to TLS 1.2
To manage notifications about this bug go to:
It's my OpenSSL, isn't it, because I am running a custom OpenSSL 1.0.2e with
ChaCha20 support:
libssl1.0.0:
Installed: 1.0.2e-0laine1
Candidate: 1.0.2e-0laine1
Version table:
*** 1.0.2e-0laine1 0
100 /var/lib/dpkg/status
1.0.1f-1ubuntu2.16 0
500
Curiously, I can't reproduce that. This is what I get:
$ openssl s_client -connect localhost:631
SSL-Session:
Protocol : TLSv1.2
Cipher: AES256-SHA256
Please attach the output of "apt-cache policy libssl1.0.0" and your
/etc/cups/cupsd.conf
Thanks!
** Information type changed
My cupsd.conf is:
#
#
# Sample configuration file for the CUPS scheduler. See "man cupsd.conf" for a
# complete description of this file.
#
# Log general information in error_log - change "warn" to "debug"
# for troubleshooting...
LogLevel notice
# Deactivate CUPS' internal logrotating, as we
