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 Ub
** Changed in: cups (Ubuntu)
Status: Invalid => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1526999
Title:
cups is intolerant to TLS 1.2
Status in cups package
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 http://ports.ubuntu.com/
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 pr
Public bug reported:
Running Ubuntu 14.04.2 LTS on armhf with lightdm version 1.10.5-0ubuntu1
The the dm-tool lock option has a typo that says "swith" instead of
"switch" in the manpage
** Affects: lightdm (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notifi
Maybe you need to make sure you home directory is owned by you, log in
through a tty and chown your home directory to your name, a incorrectly
owned .Xauthority or .ICEauthority could be the problem
** Changed in: lightdm (Ubuntu)
Status: New => Incomplete
--
You received this bug notific
6 matches
Mail list logo
