** Summary changed:
- [UBUNTU 20.04] zlib: inflate() does not update strm.adler if DFLTCC is used
+ [FFe][UBUNTU 20.04] zlib: inflate() does not update strm.adler if DFLTCC is
used
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Reading the upstream bugs, this might still be worth backporting, but
since python-cryptography has implemented a workaround and it's been
sitting here for a while this isn't critical.
** Changed in: openssl (Ubuntu)
Importance: Undecided => Medium
** Changed in: openssl (Ubuntu)
I can confirm the issue on an *old* GCP instance:
$ mount | grep devtmp
devtmpfs on /dev type devtmpfs
(rw,relatime,size=490260k,nr_inodes=122565,mode=755,inode64)
$ cat /etc/cloud/build.info
build_name: server
serial: 20200902
$ uname -a
Linux mx1 5.15.0-1018-gcp #24~20.04.1-Ubuntu SMP Mon
** Changed in: systemd (Ubuntu Kinetic)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1991829
Title:
machinectl read-only does not work
** Tags added: foundations-triage-discuss
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1991761
Title:
Backport packages for 22.04.2 HWE stack
Status in directx-headers
Looking at the attached journal logs, there's a lot of Yubikey service
activity between the lid closed and lid opened lines. Do you use a
third-party package to handle your Yubikey, by any chance?
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
--
You received this bug
** Changed in: systemd (Ubuntu)
Importance: Undecided => High
** Changed in: systemd (Ubuntu Jammy)
Importance: Undecided => High
** Changed in: systemd (Ubuntu Jammy)
Status: New => Triaged
** Tags added: foundations-triage-discuss
--
You received this bug notification because
Marking this as invalid, as the correct way to install libcap2 in Ubuntu
would be to use the package manager to do so, e.g. `apt install
libcap2`.
Glad that the issue was eventually resolved, though :)
** Changed in: libcap2 (Ubuntu)
Status: New => Invalid
--
You received this bug
** Changed in: libcap2 (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libcap2 in Ubuntu.
https://bugs.launchpad.net/bugs/1899103
Title:
libpam-cap causes PAM applications to
** Patch added: "openssl.diff"
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1991771/+attachment/5621368/+files/openssl.diff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
Public bug reported:
There's an upcoming security release for OpenSSL according to
https://mta.openssl.org/pipermail/openssl-users/2022-October/015477.html
The timing is somewhat unfortunate given our own release schedule.
The current version of openssl in kinetic, 3.0.5-2ubuntu1, is actually a
Thanks, uploaded :)
** Changed in: p11-kit (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to p11-kit in Ubuntu.
https://bugs.launchpad.net/bugs/1991067
Title:
p11-kit
** Changed in: p11-kit (Ubuntu)
Assignee: (unassigned) => Simon Chopin (schopin)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to p11-kit in Ubuntu.
https://bugs.launchpad.net/bugs/1991067
Title:
p11-kit 0.2
Marking as Won't Fix as this was reported for a series that's now
unsupported (Xenial)
** Changed in: p11-kit (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to p11-kit in Ubuntu.
** Changed in: p11-kit (Ubuntu)
Status: New => Triaged
** Changed in: p11-kit (Ubuntu)
Importance: Undecided => High
** Changed in: p11-kit (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
[335842.604] (WW) glamor: Failed to allocate 128x88 FBO due to GL_OUT_OF_MEMORY.
[335842.604] (WW) glamor: Expect reduced performance.
[335844.555] (EE) glamor0: GL error: GL_OUT_OF_MEMORY in glMapBuffer(map failed)
followed by
[335844.561] (EE) glamor0: GL error: GL_INVALID_OPERATION in
** Changed in: systemd (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1989969
Title:
autopkgtest TEST-36-NUMAPOLICY
** Changed in: systemd (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1990187
Title:
systemd-resolved recommends
** Changed in: systemd (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1990278
Title:
systemd-resolved not included in
Out of curiosity, would it work if you rename Vidéos into Videos?
** Also affects: glib2.0 (Ubuntu Jammy)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to glib2.0 in Ubuntu.
*** This bug is a duplicate of bug 1990216 ***
https://bugs.launchpad.net/bugs/1990216
** This bug has been marked a duplicate of bug 1990216
backport fix for "OpenSSL 3 cannot decrypt data encrypted with OpenSSL 1.1
with blowfish in OFB or CFB modes" to Jammy
--
You received this bug
** Changed in: openssl (Ubuntu Jammy)
Importance: Medium => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1990216
Title:
backport fix for "OpenSSL 3 cannot
I plan on reviewing and sponsoring this.
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Simon Chopin (schopin)
** Changed in: systemd (Ubuntu)
Status: New => In Progress
** Changed in: systemd (Ubuntu)
Importance: Undecided => High
--
You received
I intend to review and sponsor enr0n's fix available in the MP.
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Simon Chopin (schopin)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
ht
** Changed in: apport (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: apport (Ubuntu Focal)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
** Also affects: openssl (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: openssl (Ubuntu)
Status: New => Confirmed
** Changed in: openssl (Ubuntu Jammy)
Status: New => Confirmed
** Changed in: openssl (Ubuntu)
Importance: Undecided => Medium
**
** Changed in: tinc (Ubuntu)
Status: New => Confirmed
** Changed in: tinc (Ubuntu)
Status: Confirmed => Invalid
** Changed in: openssl (Ubuntu)
Status: New => Confirmed
** Also affects: openssl (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects:
** Changed in: openssl (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1983665
Title:
Problem loading private RSA key with pkcs11
Public bug reported:
The desktop session is running for 0 or more days. Suddenly the X server
dies, and login screen reappears.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: libgl1-mesa-dri 22.0.5-0ubuntu0.1
ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
Uname: Linux
I just tried it on all releases up to Kinetic, they're all affected. I
suspect it's actually a bug in systemd-networkd, as the files generated
in /run/systemd/networkd/ look sane enough:
root@firm-mayfly:~# cat /run/systemd/network/10-netplan-eno1.network
[Match]
MACAddress=00:16:3e:10:7a:c2
@dragu-stelian, you do not have the same issue. Looking at your logs, it
seems your client cannot reach your server over the network. This is not
related to openssl. If it were, the issue would manifest no matter from
where you're attempting to connect.
--
You received this bug notification
Hi!
I apologize, I thought I'd sent here the gameplan for the issue, but it
must have only been discussed out of band within the team. As noted by
Robie, the consensus is not to change the default configuration, but
instead patching node.js on Jammy (patches welcome for that one though).
I've
As of version 121+compat0.1-1, the relationship between packages has
changed to this:
* polkitd always requires polkitd-javascript and duktape, and always
interprets JavaScript policies
* polkitd-pkla is now an optional addon (the upstream polkit-pkla-compat
project, as shipped in e.g. Fedora)
I verified the upload on Jammy, Focal and Bionic via fresh LXC
containers, using the attached script.
For the ESM releases, it has been handled by sbeattie from the Security
Team. As I understand, the packages are already available in the ESM
security PPA (I don't have access to it).
**
Apologies for the metadata bug traffic, I hadn't realized there were
duplicates, and actually use different bug numbers in the SRU and devel
uploads. Marking this manually as released on Kinetic, as the SRU
uploads use this bug number.
** Changed in: tzdata (Ubuntu Kinetic)
Status: Triaged
*** This bug is a duplicate of bug 1986984 ***
https://bugs.launchpad.net/bugs/1986984
** This bug has been marked a duplicate of bug 2022
iso-codes is not available for breezy
** This bug is no longer a duplicate of bug 2022
iso-codes is not available for breezy
** Description
Public bug reported:
Imported from Debian bug http://bugs.debian.org/984297:
Package: src:presage
Version: 0.9.1-2.2
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-11
[This bug is not targeted to the upcoming bullseye release]
Please keep this issue
** Changed in: tzdata (Ubuntu Kinetic)
Importance: Undecided => High
** Changed in: tzdata (Ubuntu Jammy)
Importance: Undecided => High
** Changed in: tzdata (Ubuntu Focal)
Importance: Undecided => High
** Changed in: tzdata (Ubuntu Bionic)
Importance: Undecided => High
** Changed
This update has been prepared in the following PPA:
https://launchpad.net/~schopin/+archive/ubuntu/tzdata
The kinetic upload has been prepared as a full merge from Debian,
however I kept the other series' diff as small as possible by doing a
plain "upstream update". Notably, I didn't pick up the
** Summary changed:
- Availability of tzdata 2022c for Ubuntu 20.04
+ [FFe] tzdata 2022c update
** Description changed:
- tzdata 2022b and 2022c were just released that includes some timezone
- changes for Chile. According to the tzdata lib listed for Ubuntu 20.04,
- the latest package is
Yup, I cherry-picked the patches already, thanks for those :).
I'm tracking down a build failure on ppc64el that's presumably caused by
gcc-12 on -O3, and once I have a solve (other than forcing -O2) I'll
post it all here.
--
You received this bug notification because you are a member of Ubuntu
Public bug reported:
Hi,
lxc currently fails to build against glibc 2.36, which also affects its
autopkgtests. Here's an excerpt of the failed build logs containing the
first error detected:
gcc -DHAVE_CONFIG_H -I. -I../../src -Wdate-time -D_FORTIFY_SOURCE=2 -fPIE
-Wvla -std=gnu11
The test case is already in the "Example output" file.
https://launchpadlibrarian.net/493705832/sudo-broken.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sudo in Ubuntu.
https://bugs.launchpad.net/bugs/1891798
Title:
Uploaded, thanks :)
** Changed in: p11-kit (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to p11-kit in Ubuntu.
https://bugs.launchpad.net/bugs/1982841
Title:
[22.10
I'll mark the bug as fix released as I think Ubuntu releases no longer
suffer from this problem. Also, all Ubuntu releases still receiving
normal support have moved away from upstart.
** Changed in: upstart (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification
** Changed in: libvpx (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libvpx in Ubuntu.
https://bugs.launchpad.net/bugs/1987051
Title:
libvpx: merge 1.12.0-1 from Debian
Public bug reported:
Merge new upstream version into kinetic.
** Affects: libvpx (Ubuntu)
Importance: High
Assignee: Simon Chopin (schopin)
Status: In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
** Changed in: openssl (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1987047
Title:
openssl: merge 3.0.5-2 from Debian
Public bug reported:
We need to merge the new version from Debian, notably because of
CVE-2022-2097 (the other security issue already being fixed as a cherry-
picked patch)
** Affects: openssl (Ubuntu)
Importance: High
Assignee: Simon Chopin (schopin)
Status: Confirmed
** Summary changed:
- dnsmasq often using 100% of CPU
+ dnsmasq often using 100% of CPU if the upstream nameserver is unreachable
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
** Package changed: tracker (Ubuntu) => tracker-miners (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tracker in Ubuntu.
https://bugs.launchpad.net/bugs/1983859
Title:
tracker-extract crashes with SIGSYS when
Public bug reported:
If an update for a package is available but not installed, simulating a
purge shows the wrong version.
On that 20.04 system, an update to libxml2 2.9.10+dfsg-5ubuntu0.20.04.4
was available but only the ".3" one was installed. Simulating a purge
gives this bogus output (with
Public bug reported:
When upgrading Ubuntu Desktop from 20.04 to 22.04, there's often (pretty
much always) a crash from tracker-extract, as described in the following
error report:
https://errors.ubuntu.com/oops/d7866d85-14cc-11ed-a52b-fa163e55efd0
The crash occurs during the upgrade, which
This bug was reported against an Ubuntu version that's long been EOL.
Please try to reproduce with a supported release and report a new bug if
appropriate. Thanks.
** Changed in: rsyslog (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a
The affected Ubuntu release is no longer supported so closing the bug.
The problem seemed like a mirror or an apt issue more than a rsyslog one
anyway.
** Changed in: rsyslog (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
This bug was reported against an Ubuntu version that's long been EOL.
Please try to reproduce with a supported release and report a new bug if
appropriate. Thanks.
** Changed in: rsyslog (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of
This bug was reported against an Ubuntu version that's long been EOL.
Please try to reproduce with a supported release and report a new bug if
appropriate. Thanks.
** Changed in: rsyslog (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of
This bug was reported against an Ubuntu version that's long been EOL.
Please try to reproduce with a supported release and report a new bug if
appropriate. Thanks.
** Changed in: rsyslog (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a
This bug was reported against an Ubuntu version that's long been EOL.
Please try to reproduce with a supported release and report a new bug if
appropriate. Thanks.
** Changed in: rsyslog (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of
This bug was reported against an Ubuntu version that's long been EOL.
Please try to reproduce with a supported release and report a new bug if
appropriate. Thanks.
** Changed in: rsyslog (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of
This bug was reported against an Ubuntu version that's long been EOL.
Please try to reproduce with a supported release and report a new bug if
appropriate. Thanks.
** Changed in: rsyslog (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a
This bug was reported against an Ubuntu version that's long been EOL.
Please try to reproduce with a supported release and report a new bug if
appropriate. Thanks.
** Changed in: rsyslog (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a
Ubuntu 22.04 with rsyslog 8.2112.0 doesn't have this problem so marking
as fixed, thanks!
** Changed in: rsyslog (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in
This bug was reported against an Ubuntu version that's long been EOL.
Please try to reproduce with a supported release and report a new bug if
appropriate. Thanks.
** Changed in: rsyslog (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a
Ubuntu 18.04 with rsyslog 8.32.0 is not affected by that problem anymore
so marking as such. Thanks.
** Changed in: rsyslog (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
This bug was reported against an Ubuntu version that's long been EOL.
Please try to reproduce with a supported release and report a new bug if
appropriate. Thanks.
** Changed in: rsyslog (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a
This bug was reported against an Ubuntu version that's long been EOL.
Please try to reproduce with a supported release and report a new bug if
appropriate. Thanks.
** Changed in: rsyslog (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a
This bug was reported against an Ubuntu version that's long been EOL.
Please try to reproduce with a supported release and report a new bug if
appropriate. Thanks.
** Changed in: rsyslog (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a
This bug was reported against an Ubuntu version that's long been EOL.
Please try to reproduce with a supported release and report a new bug if
appropriate. Thanks.
** Changed in: rsyslog (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a
Marking as fix released based on versions reported in comment # 10.
Ubuntu Trusty ships 7.4.4 so it has the patch.
** Changed in: rsyslog (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
This bug was reported against an Ubuntu version that's long been EOL.
Please try to reproduce with a supported release and report a new bug if
appropriate. Thanks.
** Changed in: rsyslog (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of
This bug was reported against an Ubuntu version that's long been EOL.
Please try to reproduce with a supported release and report a new bug if
appropriate. Thanks.
** Changed in: rsyslog (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of
This bug was reported against an Ubuntu version that's long been EOL.
Please try to reproduce with a supported release and report a new bug if
appropriate. Thanks.
** Changed in: rsyslog (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of
** Changed in: rsyslog (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
https://bugs.launchpad.net/bugs/583936
Title:
package rsyslog-mysql 4.2.0-2ubuntu8
This bug was reported against an Ubuntu version that's long been EOL.
Please try to reproduce with a supported release and report a new bug if
appropriate. Thanks.
** Changed in: rsyslog (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of
This bug was reported against an Ubuntu version that's long been EOL.
Please try to reproduce with a supported release and report a new bug if
appropriate. Thanks.
** Changed in: rsyslog (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a
This bug was reported against an Ubuntu version that's long been EOL.
Please try to reproduce with a supported release and report a new bug if
appropriate. Thanks.
** Changed in: rsyslog (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of
This bug was reported against an Ubuntu version that's long been EOL.
Please try to reproduce with a supported release and report a new bug if
appropriate. Thanks.
** Changed in: rsyslog (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of
This bug was reported against an Ubuntu version that's long been EOL.
Please try to reproduce with a supported release and report a new bug if
appropriate. Thanks.
** Changed in: rsyslog (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of
This bug was reported against an Ubuntu version that's long been EOL.
Please try to reproduce with a supported release and report a new bug if
appropriate. Thanks.
** Changed in: rsyslog (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of
This bug was reported against an Ubuntu version that's long been EOL.
Please try to reproduce with a supported release and report a new bug if
appropriate. Thanks.
** Changed in: rsyslog (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of
This bug was reported against an Ubuntu version that's long been EOL.
Please try to reproduce with a supported release and report a new bug if
appropriate. Thanks.
** Changed in: rsyslog (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of
This bug was reported against an Ubuntu version that's long been EOL.
Please try to reproduce with a supported release and report a new bug if
appropriate. Thanks.
** Changed in: rsyslog (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of
This bug was reported against an Ubuntu version that's long been EOL.
Please try to reproduce with a supported release and report a new bug if
appropriate. Thanks.
** Changed in: rsyslog (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of
This bug was reported against an Ubuntu version that's long been EOL.
Please try to reproduce with a supported release and report a new bug if
appropriate. Thanks.
** Changed in: rsyslog (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of
This bug was reported against an Ubuntu version that's long been EOL.
Please try to reproduce with a supported release and report a new bug if
appropriate. Thanks.
** Changed in: rsyslog (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of
This bug was reported against an Ubuntu version that's long been EOL.
Please try to reproduce with a supported release and report a new bug if
appropriate. Thanks.
** Changed in: rsyslog (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of
This bug was reported against an Ubuntu version that's long been EOL.
Please try to reproduce with a supported release and report a new bug if
appropriate. Thanks.
** Changed in: rsyslog (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of
This bug was reported against an Ubuntu version that's long been EOL.
Please try to reproduce with a supported release. Marked as incomplete
until then. Thanks.
** Changed in: rsyslog (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of
** Description changed:
- [Impact]
- While the default configuration works fine for every package that uses the
system libssl3, any software that uses libssl1.1, either separately packaged
(e.g. as an upgrade leftover) or vendored in (as in nodejs in our own archive)
will fail to load the
Many thanks for raising this :)
I was prepared to argue for this change as (if working as intended) it
has basically no impact on our own applications and could help quite a
few unsuspecting users, but since you asked for evidence I did a little
digging, and was somewhat surprised by what I
** Tags added: fr-2537
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to nettle in Ubuntu.
https://bugs.launchpad.net/bugs/1959469
Title:
[22.10 FEAT] Upgrade nettle to latest version >= 3.7.4 (crypto)
Status in Ubuntu on
** Description changed:
+ [Impact]
+ While the default configuration works fine for every package that uses the
system libssl3, any software that uses libssl1.1, either separately packaged
(e.g. as an upgrade leftover) or vendored in (as in nodejs in our own archive)
will fail to load the
I'm just watching from the sidelines here, but why do we need to have
a transition for this? Is there an ABI break I'm not aware of? Or is zlib
usually statically linked in Debian packages?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
*** This bug is a duplicate of bug 1940141 ***
https://bugs.launchpad.net/bugs/1940141
** This bug has been marked a duplicate of bug 1940141
OpenSSL servers can send a non-empty status_request in a CertificateRequest
--
You received this bug notification because you are a member of
On a fresh Jammy LXC container:
root@rational-polliwog:~# dpkg -l libssl-dev | tail -n 1
ii libssl-dev:amd64 3.0.2-0ubuntu1.4 amd64Secure Sockets Layer toolkit
- development files
root@rational-polliwog:~# cat < openssl_test.c
#include
int main()
{
EVP_PKEY_Q_keygen(NULL, NULL,
On a fresh Jammy LXC container:
root@rational-polliwog:~# dpkg -l openssl | tail -n 1
ii openssl3.0.2-0ubuntu1.4 amd64Secure Sockets Layer toolkit -
cryptographic utility
root@rational-polliwog:~# openssl s_server -nocert -psk 01020304 -dtls1
Using default temp DH parameters
Just to confirm, on a fresh LXC Jammy container:
root@rational-polliwog:~# dpkg -l openssl | tail -n 1
ii openssl3.0.2-0ubuntu1.4 amd64Secure Sockets Layer toolkit -
cryptographic utility
root@rational-polliwog:~# grep SECLEVEL /etc/ssl/openssl.cnf
CipherString =
You'll need to contact your provider. I'm guessing their script isn't
compatible with OpenSSL 3.0, but without more information (such as the
stdout/stderr of the openssl CLI invocation here) there isn't much we
can do on this end.
Whatever the precise issue though, it's almost certainly NOT
https://launchpad.net/ubuntu/+source/openssl/3.0.2-0ubuntu1.4 builds
fine, marking it as jammy-verified.
** Tags removed: verification-needed-jammy
** Tags added: verification-done-jammy
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
201 - 300 of 1674 matches
Mail list logo
