This bug affects me too, with a client certificate that now "magically"
does not match the requirements.
Ironically, the error message says only:
OpenSSL error error:140AB18E:SSL routines:SSL_CTX_use_certificate:ca md
too weak, (no key found, wrong pass phrase, or wrong file format?)
although
I cannot tell if this is a problem in whatever version of Debian, since
I do not use it.
Even with Ubuntu being derived from Debian at some point between 18.04
where /etc/securetty was delivered with package login and 20.04 where
the whole package is unavailable.
I think that is an
At least, in 18.04, the file /etc/securetty was in package login...
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to shadow in Ubuntu.
https://bugs.launchpad.net/bugs/1872443
Title:
/etc/securetty missing: dovecot not
Public bug reported:
With Ubuntu 20.04 Focal Fossa, /etc/securetty is missing from the
"login" package (4.8.1-1ubuntu4).
This leads to errors such as in /var/log/mail.log when a dovecot auth is
tried:
Apr 13 13:08:17 venus dovecot[10588]: imap-login: Login: user=,
method=PLAIN,
Never mind. My fault. The journal was gone, so nothing could be shown.
** Changed in: systemd (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Public bug reported:
Software versions:
# lsb_release -rd
Description:Ubuntu Focal Fossa (development branch)
Release:20.04
# apt-cache policy systemd
systemd:
Installed: 244.3-1ubuntu1
Candidate: 244.3-1ubuntu1
Version table:
*** 244.3-1ubuntu1 500
500
** Description changed:
While I welcome the adding of security features by upgrading vital packages
like openssl,
there are at least two packages that I know of which ran fine with libssl
1.1.0 and do not with libssl 1.1.1. This bug has been introduced with the
migration from openssl 1.1.0
Public bug reported:
While I welcome the adding of security features by upgrading vital packages
like openssl,
there are at least two packages that I know of which ran fine with libssl 1.1.0
and do not with libssl 1.1.1. This bug has been introduced with the migration
from openssl 1.1.0 to
Hi,
good idea in theory, but I want to add my 2cents: Please coordinate this
update with ALL affected packages, like apache2 and nginx.
My reason is:
I just tried the PPA and found that nginx works with TLS 1.3 after that
right out of the box.
HOWEVER, there is a problem: openssl 1.1.1 has
9 matches
Mail list logo
