This bug was fixed in the package pam - 1.3.1-5ubuntu4.3
---
pam (1.3.1-5ubuntu4.3) focal; urgency=medium
* Correctly document current VCS in debian/control.
* Drop patches to implement "nullok_secure" option for pam_unix.
Closes: #674857, #936071, LP: #1860826.
*
** Bug watch removed: Debian Bug tracker #931899
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931899
** Bug watch removed: Debian Bug tracker #674857
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674857
** Changed in: pam (Ubuntu Focal)
Importance: Undecided => Low
--
You
Worked for me on my daily workstation:
⏚ [sarnold:~/trees] 100 $ sudo apt install -tfocal-proposed libpam0g
libpam-runtime libpam-modules-bin libpam-modules
Reading package lists... Done
Building dependency tree
Reading state information... Done
Recommended packages:
update-motd
The
It works:
# witness the original bug while running `sudo -i` in another session:
sdeziel@xeon:~$ tail -f /var/log/auth.log | grep pam
Sep 28 16:56:52 xeon sudo: pam_unix(sudo:auth): Couldn't open /etc/securetty:
No such file or directory
Sep 28 16:56:53 xeon sudo: pam_unix(sudo:session): session
Hello Seth, or anyone else affected,
Accepted pam into focal-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/pam/1.3.1-5ubuntu4.3
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Description changed:
- Hello, after upgrading to focal I found the following in my journalctl
- output:
+ [Impact]
+ Removal of the /etc/securetty file from the system results in useless log
messages whenever pam_unix is invoked, which for some systems is quite a lot of
logging.
** Changed in: pam (Ubuntu Focal)
Status: Confirmed => In Progress
--
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/1860826
Title:
pam_unix(sudo:auth): Couldn't open
This bug was fixed in the package pam - 1.3.1-5ubuntu11
---
pam (1.3.1-5ubuntu11) impish; urgency=medium
* extrausers.patch: update for compatibility with the removal of
nullok_secure.
-- Steve Langasek Wed, 15 Sep 2021
22:39:58 -0700
** Changed in: pam (Ubuntu)
** Changed in: pam (Ubuntu Groovy)
Status: Confirmed => Won't Fix
** Changed in: pam (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pam in Ubuntu.
This also spams the vsftpd log several times per minute
--
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/1860826
Title:
pam_unix(sudo:auth): Couldn't open /etc/securetty: No
After I upgraded libpam-runtime from 1.3.1-5ubuntu4.1 to
1.3.1-5ubuntu4.2, I also met this error.
--
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/1860826
Title:
** Changed in: pam (Ubuntu Focal)
Status: New => Confirmed
--
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/1860826
Title:
pam_unix(sudo:auth): Couldn't open
I'm adding a Focal task as requested in #ubuntu-bugs. However, please
don't take this as an endorsement for a Focal SRU. If it's just spurious
log entries, I'm not sure if an SRU would be appropriate or not.
** Also affects: pam (Ubuntu Focal)
Importance: Undecided
Status: New
--
You
** Changed in: pam (Debian)
Status: New => Fix Released
--
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/1860826
Title:
pam_unix(sudo:auth): Couldn't open
In fact the comments above explicitly say "Closes: #674857, #936071, LP:
#1860826 [this bug]".
--
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/1860826
Title:
Despite what Launchpad is showing here, the upstream Debian bugs were
fixed over a month ago:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936071#23
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674857#61
Ubuntu maintainers: please add the "Focal" series for this bug.
--
You received
It also appears to affect cups.
# systemctl status cups.service
● cups.service - CUPS Scheduler
Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset:
enabled)
Active: active (running) since Thu 2020-11-05 15:45:21 EST; 32min ago
TriggeredBy: ● cups.path
On Tue, Oct 27, 2020 at 03:49:30AM -, Zach H wrote:
> Hi, just to confirm that this may be a bigger issue than first
> anticipated - on Ubuntu Server 20.04 this is causing issues with logins
> via sftp/ftp.
Why do you believe your issue is caused by this bug? The only known effect
of this
Hi, just to confirm that this may be a bigger issue than first
anticipated - on Ubuntu Server 20.04 this is causing issues with logins
via sftp/ftp. Because of this, the migration of a number of our servers
has had to be halted until this bug has been completed. Copy-pasting the
Securetty file
I am still seeing this in Ubuntu 20.04.1:
Oct 23 17:29:10 comp gdm-password][1766]: pam_unix(gdm-password:auth):
Couldn't open /etc/securetty: No such file or directory
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pam in
** Tags added: fr-14
--
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/1860826
Title:
pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or
directory
Status in
> No, it would not. The sum totality of the impact of this bug is the extra
warning messages in the log files.
Damn...
--
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/1860826
On Tue, Sep 01, 2020 at 01:53:00AM -, Sterling Butters wrote:
> Would this bug cause a gnome-session initialization delay?
No, it would not. The sum totality of the impact of this bug is the extra
warning messages in the log files.
--
You received this bug notification because you are a
Would this bug cause a gnome-session initialization delay? My logs have
this error and technically everything "works" correctly but
initialization of the user session takes > 1 min. The greeter isn't
exactly fast either but definitely more tolerable. My systemd analysis
looks fine too. Really
On Thu, Aug 27, 2020 at 06:02:33PM -, bood wrote:
> does it cause the lock screen to freeze during unlock?
No. Please file a separate bug for your issue.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pam in Ubuntu.
does it cause the lock screen to freeze during unlock?
My lock screen during unlock freezes occasionally (once every 2 weeks), and
this is one of 3 logs having recent updates:
Aug 27 18:37:02 PCName gdm-password]: pam_unix(gdm-password:auth): Couldn't
open /etc/securetty: No such file or
Same here after focal Update with local sudoers. With sudoers over
ActiveDirectory (SSS) it is working, but all local entries are ignored
@20.04.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pam in Ubuntu.
So is it safe for an user to just remove "nullok_secure" as suggested in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931899 ?
** Bug watch added: Debian Bug tracker #931899
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931899
--
You received this bug notification because you are a
** Tags removed: champagne
--
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/1860826
Title:
pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or
directory
Joshua, it's not a typo, and not a missing dependency:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674857#25
Thanks
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pam in Ubuntu.
I would say there is probably a missing dependency-/etc/securetty
doesn't exist in Ubuntu and looks like it could be a typo.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pam in Ubuntu.
** Tags added: id-5ebd60b9e10a724ad7cbaffe
--
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/1860826
Title:
pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or
** Also affects: pam (Ubuntu Groovy)
Importance: Low
Status: Confirmed
--
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/1860826
Title:
pam_unix(sudo:auth): Couldn't
** Changed in: pam (Debian)
Status: Unknown => 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/1860826
Title:
pam_unix(sudo:auth): Couldn't open /etc/securetty: No
** Bug watch added: Debian Bug tracker #936071
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936071
** Changed in: pam (Debian)
Remote watch: Debian Bug tracker #674857 => Debian Bug tracker #936071
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
@seb128 reading the referenced bug further reveals that I'm waiting for
PAM maintainers' input on this.
** Bug watch added: Debian Bug tracker #674857
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674857
** Also affects: pam (Debian) via
Looks like Balint has been looking at that problem from the Debian side,
assigning to him
@Balint, feel free to unassign if I got that wrong :)
** Changed in: pam (Ubuntu)
Importance: Undecided => Low
** Changed in: pam (Ubuntu)
Status: New => Confirmed
** Changed in: pam (Ubuntu)
** Tags added: champagne
--
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/1860826
Title:
pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or
directory
Status
38 matches
Mail list logo
