Tested pam_faillock module for pam on bionic.
Test consisted on setting up pam_faillock with the following
configuration, as described in the man page:
/etc/security/faillock.conf file example:
deny=4
unlock_time=1200
silent
/etc/pam.d/config file example:
auth required pam_faillock.so
Additional tests done on bionic: after changing the parameters set in
/etc/security/faillock.conf to:
deny=2
unlock_time=20
By trying to authenticate with the wrong password 2 times, it was
verified that the account was locked for the amount of time set to the
unlock_time parameter (20s).
--
Yo
By following the same test procedure done in #18 and #19, the Focal
build of pam_faillock was successfully validated.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1927796
Title:
[SRU]pam_tally2 can
By following the same test procedure done in #18 and #19, the Groovy
build of pam_faillock was successfully validated.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1927796
Title:
[SRU]pam_tally2 ca
By following the same test procedure done in #18 and #19, the Hirsute
build of pam_faillock was successfully validated.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1927796
Title:
[SRU]pam_tally2 c
Public bug reported:
[IMPACT]
There is a known issue in pam_tally2 which may cause an account to be lock down
even with correct password, in a busy node environment where simultaneous
logins takes place (https://github.com/linux-pam/linux-pam/issues/71).
There are already two customer cases fro
** Changed in: nss (Ubuntu)
Assignee: (unassigned) => Richard Maciel Costa (richardmaciel)
** Changed in: nss (Ubuntu Bionic)
Assignee: (unassigned) => Richard Maciel Costa (richardmaciel)
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
Reviewed patches and they look good to me.
However, in the future, we should consider another possibility: disable
FIPS mode for libNSS3 by default, since that lib isn't FIPS-certified.
This can prevent customers from mistakenly think the opposite.
--
You received this bug notification because
** Changed in: ubuntu-advantage-tools (Ubuntu)
Assignee: (unassigned) => Richard Maciel Costa (richardmaciel)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1942010
Title:
Ensure lockout
Hi, is it possible to get a copies of the '/etc/pam.d/common-auth' and
'/etc/pam.d/common-account' files?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1942010
Title:
Ensure lockout for failed passw
Hi, the attached files don't look like ones that were changed by the USG
hardening script. Specially because the hardening scripts add the
pam_tally2 files in specific places. Below is the script code:
#
#5.3.2 Ensure
** Changed in: ubuntu-advantage-tools (Ubuntu)
Assignee: (unassigned) => Richard Maciel Costa (richardmaciel)
** Changed in: ubuntu-advantage-tools (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
Hey @scott-mackenzie, any news about this bug? I really could not
reproduce it using multipass images, or the newest images downloaded
from the ubuntu site and installed on QEMU VMs.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http
Hey @scott-mackenzie, any news about this bug? I really could not
reproduce it using multipass images, or the newest images downloaded
from the ubuntu site and installed on QEMU VMs.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http
14 matches
Mail list logo
