Your message dated Mon, 5 Apr 2021 21:49:47 +0200
with message-id
<CAK0OdpzSe815iTXG7YvV=FekjU0=j_2xgmmepgldl-yvhmc...@mail.gmail.com>
and subject line Re: Bug#932458: Couldn't open /etc/securetty: No such file or
directory
has caused the Debian Bug report #932458,
regarding pam_unix complains about removal of /etc/securetty
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
932458: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932458
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: shadow
Version: 1:4.7-1
Severity: normal
Hi,
Since 1:4.7-1, /etc/securetty is not present on the system anymore and
since then pam_unix complains that the file is missing:
sudo[11488]: pam_unix(sudo:auth): Couldn't open /etc/securetty: Aucun fichier
ou dossier de ce type
Was this removal coordinated with PAM package?
Kind regards,
Laurent Bigonville
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1,
'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-5-amd64 (SMP w/8 CPU cores)
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8),
LANGUAGE=fr_BE:fr (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Control: reassign -1 pam 1.3.1-5
Control: fixed -1 pam 1.4.0-1
Hi Chris,
Chris Hofstaedtler <[email protected]> ezt írta (időpont: 2020. dec.
31., Cs, 0:56):
>
> Hey,
>
> * Bálint Réczey <[email protected]> [201230 23:53]:
> > Bálint Réczey <[email protected]> ezt írta (időpont: 2019. nov.
> > 7., Cs, 20:45):
> > > Thorsten Glaser <[email protected]> ezt írta (időpont: 2019. nov. 6.,
> > > Sze, 23:08):
> > > >
> > > > Hi everyone,
> > > >
> > > > when will something happen to not fill syslog with these messages
> > > > (unless deserved, such as if there is really something to warn about)?
> > > >
> > > > It’s not even stated yet whether the suggested change to the config
> > > > is safe to apply…
> > >
> > > I'm waiting for Steve's position on this. I believe the change to
> > > shadow was OK and all we need is removing the message in PAM.
> > > Since it is a trivial change I have not prepared a patch but I'm happy
> > > to if Steve prefers that.
> >
> > I asked upstream if they just want to silence the notice, but they
> > don't want to:
> > https://github.com/linux-pam/linux-pam/pull/158
> >
> > It leaves us with disabling it using configuration files. IMO the
> > proposed patch of removing nullok_secure is safe and the desired
> > solution.
> > However it is up to the maintainers, Steve, or Sam, to accept the
> > patch unless someone NMUs it.
> > I don't plan NMU-ing it myself, but since the general NMU rules apply
> > any DD can NMU it via DELAYED/10.
>
> Given not much has happened so far, maybe login should remove
> pam_securetty from its default PAM configuration instead?
>
> Thats nothing that needs to be coordinated with the PAM maintainers,
> AFAICT.
It seems this is fixed in pam.
Cheers,
Balint
--- End Message ---
