The --disable flag does not exist in Jammy, it was introduced in PAM
1.5.2-6 https://tracker.debian.org/news/1405352/accepted-
pam-152-6-source-into-unstable/
The two files are the same which is probably not intended as they will add the
same entries twice.
Using the below config, `pam auth-upda
Hi Simon, ok.
It was my initial plan to open it under ws4py but since the bug breaks pylxd
functionality substantially, and is present on a default LTS installation and
doesn't have a simple mitigation, I opened the bug there for better visibility.
** Bug watch added: github.com/canonical/pylxd/
Linking related issue on github:
https://github.com/canonical/pylxd/issues/585
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2084973
Title:
containers.execute() fails on Python3.12+
To manage notif
** Summary changed:
- containers.exeute() fails on Python3.12+
+ containers.execute() fails on Python3.12+
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2084973
Title:
containers.execute() fails on
** Description changed:
When trying to execute a command on a container with pylxd (on Ubuntu
24.04.1 / Python 3.12.3), the following exception is raised:
```
Traceback (most recent call last):
- File "/home/user/test.py", line 20, in
- instance.execute(['hostname'])
- File "/u
Public bug reported:
When trying to execute a command on a container with pylxd (on Ubuntu
24.04.1 / Python 3.12.3), the following exception is raised:
```
Traceback (most recent call last):
File "/home/user/test.py", line 20, in
instance.execute(['hostname'])
File "/usr/lib/python3/dist
I narrowed down the issue to 'ceph-*.target' unit files (e.g. ceph-mds.target,
ceph-mon.target).
The unit files list 'ceph.target' both in the "Wants" and the "WantedBy"
directives, which trigger the
bug in OpenSCAP. If either of the directives are removed, OpenSCAP no longer
crashes:
---
[Unit
I reviewed libmail-dmarc-perl 1.20230215-1 as checked in noble. This shouldn't
be considered a full
audit but rather a quick gauge of maintainability.
libmail-dmarc-perl is a Perl module implementing DMARC. It can be used by:
- MTAs and filtering tools like SpamAssassin to **validate** that incom
I reviewed libemail-mime-perl 1.953-1 as checked into noble. This shouldn't be
considered a full audit but rather a quick gauge of maintainability.
libemail-mime-perl is a Perl module (Email::MIME), an extension of the
Email::Simple module, to handle MIME encoded messages. It takes a message
as a
Hi all,
During the security review I noticed that several dependencies for this package
were replaced with those that already exist in main:
- Net::IDN::Encode -> Net::LibIDN [1]
- Email::MIME -> MIME::Parser & MIME::Entity [2]
To my understanding, this was done to avoid introducing unnecessary a
10 matches
Mail list logo
