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 th
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 interdependenc
Not a bug in Ubuntu
** Changed in: dovecot (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/1872550
Title:
dovecot snarfing does not work on 20.04
To manage not
My bad: It does not work with the current dovecot 2.3.10 from the official
repos, either.
Thus, it is an upstream bug.
I have found how to solve the problem:
mail_location = mbox:/home/%u/mail/:INBOX=/home/%u/mail/mbox:INDEX=MEMORY
mail_plugins = snarf notify zlib
namespace Snarf {
prefi
Public bug reported:
Description:Ubuntu Focal Fossa (development branch)
Release:20.04
Package:dovecot (2.3.7.2-1ubuntu3)
Problem:
When using "snarf", the dovecot version delivered with 20.04 (Focal
Fossa) does not work correctly. Snarfing is used to get new mail from
/var/ma
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872443
Title:
/etc/securetty missing: dovecot not working
To manage notifications
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,
rip=192.168.123.
I hope that the upstream patch will be in time for Focal Fossa
finalisation.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872288
Title:
Focal Fossa: postfix configure-instance script typos
To man
Public bug reported:
Description:Ubuntu Focal Fossa (development branch)
Release:20.04
Postfix 3.4.10-1
There are some typos that have crept into
/usr/lib/postfix/configure-instance.sh which keep the postfix chroot
environment from working.
In the script, there are two sections t
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867784
Title:
"sy
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 http://de.archiv
** 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 1.1.
Public bug reported:
stunnel4 breaks with openssl 1.1.1 which supports TLS 1.3. This bug has
been introduced with the migration from openssl 1.1.0 in one of the last
point releases.
I get errors when a Windows stunnel client connects to the stunnel4
daemon:
Feb 20 14:10:03 peterpan.neverland stu
apport information
** Attachment added: "PciMultimedia.txt"
https://bugs.launchpad.net/bugs/1851382/+attachment/5303083/+files/PciMultimedia.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/18513
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1851382/+attachment/5303088/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1851382
Title:
Mi
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1851382/+attachment/5303081/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1851382
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1851382/+attachment/5303089/+files/WifiSyslog.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1851382/+attachment/5303086/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/185
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1851382/+attachment/5303082/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1851382
Title:
Miss
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1851382/+attachment/5303085/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1851382
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1851382/+attachment/5303084/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
apport information
** Tags added: apport-collected bionic
** Description changed:
There are two essential kernel modules that are missing from some linux
kernel packages under Ubuntu Server 18.04 LTS:
nfsv4.ko and aes-x86_64.ko (matter-of-fact any crypto module)
I found them both m
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1851382/+attachment/5303087/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1851382
Public bug reported:
There are two essential kernel modules that are missing from some linux
kernel packages under Ubuntu Server 18.04 LTS:
nfsv4.ko and aes-x86_64.ko (matter-of-fact any crypto module)
I found them both missing in linux-kvm and nfsv4.ko missing in linux-
generic - both are prese
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 chan
Public bug reported:
With Bionic (18.04), libcurl4 is the standard, libcurl3 seems to be a
compatibility library.
However, libcurl3 and libcurl4 can not be installed together, presumably
because of some obscure dependencies in the packages. These dependencies
are, however, unneccessary, because t
There is an even better fix, however, something like this should be
included in the Ubuntu documentation for x11vnc as it is far from
obvious...
One can put something like this into /usr/share/sddm/scripts/Xsetup:
/usr/bin/x11vnc -rfbauth /etc/vncpasswd -rfbport 5943 -reopen -forever &
Explanati
Oh, and BTW: There will be no upstream fix for this, see:
https://github.com/sddm/sddm/issues/622
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1566542
Title:
[upstream] Two sddm bugs with 16.04 – M
The versions are correct.
I doubt that the update of x11vnc would change anything with regard to the
interoperability issue.
As a workaround for that, I resorted to use:
ExecStart=/bin/sh -c '/usr/bin/x11vnc -auth /var/run/sddm/* -display :0
-rfbauth /etc/vncpasswd -rfbport 5943 -reopen -forev
Public bug reported:
SDDM with 16.04 LTS introduces two new problems that did not exist with
15.10 or 14.04:
1. The option HideShells in /etc/sddm.conf does not work correctly. When
more than one shell is specified, the filter does not work and the
matching users are listed in the greeting screen
31 matches
Mail list logo
