Public bug reported:
An SSH terminal into an Ubuntu server (tested on 18.04.5) hangs running
a command using 'sudo' when 'use_pty' is set in /etc/sudoers.
Steps to reproduce ('sudo' version --> 1.8.21p2-3ubuntu1.2):
1) Log in into an Ubuntu server (tested on 18.04.5 using SSH)
2) Ensure that
** Description changed:
An SSH terminal into an Ubuntu server (tested on 18.04.5) hangs running
a command using 'sudo' when 'use_pty' is set in /etc/sudoers.
- Steps to reproduce:
+ Steps to reproduce ('sudo' version --> 1.8.21p2-3ubuntu1.2):
1) Log in into an Ubuntu server (tested on
** Description changed:
An SSH terminal into an Ubuntu server (tested on 18.04.5) hangs running
a command using 'sudo' when 'use_pty' is set in /etc/sudoers.
Steps to reproduce ('sudo' version --> 1.8.21p2-3ubuntu1.2):
1) Log in into an Ubuntu server (tested on 18.04.5 using SSH)
** Also affects: sudo (Ubuntu Bionic)
Importance: Undecided
Status: New
--
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/1895757
Title:
Terminal hangs running sudo
Public bug reported:
A customer reported network disconnections on their storage
servers when running 'netplan apply'. The culprit was that
they have link-local addresses configured and the Duplicate
Address Detection (DAD) mechanism was delaying the interfaces
from coming back up.
As a
I agree, a user-configured setting should be honored. Another thing to
consider is that according to the Jammy systemd.network man page, the
default should be 'ipv6' so one would expect that to be a global
default, but it gets overridden for link-local IPs due to this commit.
[1]
Tested 249.11-0ubuntu3.3 and DuplicateAddressDetection is now honored as
expected. No other issues were observed.
--
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/1964494
Public bug reported:
When pam_pwhistory is in use non-root users are unable to change their
passwords. In fact, they are able to change it but the system spits out
an error even though the password was indeed changed.
Reproducer:
---
1. created an Ubuntu/Focal VM
2. added a user 'test'
** Also affects: ubuntu-security-certifications
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pam in Ubuntu.
https://bugs.launchpad.net/bugs/1989731
Title:
Non-root user unable
It seems like if the line:
'password required pam_pwhistory.so remember=5'
is added before the pam_unix line in /etc/pam.d/common-password
everything works as expected because the new password now won't match the "old"
password that was already in the shadow file (which is what happens if
The CIS recommendations containing the fix for this issue have been
already released [1][2].
The next step would be to fix the CIS/USG tooling so that it follows the
new guidelines.
[1] https://workbench.cisecurity.org/benchmarks/11909
[2]
11 matches
Mail list logo
