Your message dated Fri, 12 Jul 2019 09:27:40 +0200 with message-id <[email protected]> and subject line Re: Bug#931899: login: still tries to open /etc/securetty has caused the Debian Bug report #931899, regarding login: still tries to open /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.) -- 931899: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931899 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: login Version: 1:4.7-1 According to the Debian changelog, login has stopped honoring /etc/securetty, but journalctl shows that it complains about the now missing file: ,---- | Jul 12 08:47:31 turtle login[1039]: pam_unix(login:auth): Couldn't open /etc/securetty: No such file or directory | Jul 12 08:47:34 turtle login[1039]: pam_unix(login:auth): Couldn't open /etc/securetty: No such file or directory | Jul 12 08:47:34 turtle login[1039]: pam_unix(login:session): session opened for user sven by LOGIN(uid=0) | Jul 12 08:47:34 turtle systemd-logind[419]: New session 1 of user sven. `---- So why does login still try to open /etc/securetty? -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.2.0-nouveau (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages login depends on: ii libaudit1 1:2.8.5-1 ii libc6 2.28-10 ii libpam-modules 1.3.1-5 ii libpam-runtime 1.3.1-5 ii libpam0g 1.3.1-5 login recommends no packages. login suggests no packages. -- no debconf information
--- End Message ---
--- Begin Message ---On 2019-07-12 09:01 +0200, Sven Joachim wrote: > Package: login > Version: 1:4.7-1 > > According to the Debian changelog, login has stopped honoring > /etc/securetty, but journalctl shows that it complains about the now > missing file: > > ,---- > | Jul 12 08:47:31 turtle login[1039]: pam_unix(login:auth): Couldn't open > /etc/securetty: No such file or directory > | Jul 12 08:47:34 turtle login[1039]: pam_unix(login:auth): Couldn't open > /etc/securetty: No such file or directory > | Jul 12 08:47:34 turtle login[1039]: pam_unix(login:session): session opened > for user sven by LOGIN(uid=0) > | Jul 12 08:47:34 turtle systemd-logind[419]: New session 1 of user sven. > `---- > > So why does login still try to open /etc/securetty? Apparently the complaints come from the pam_securetty module which for some reason is enabled by default, although I could not find any reference to it in /etc/pam.d. Seems there is nothing login can do about that, so I'm closing this bug. I will follow up on bug #674857 later. Cheers, Sven
--- End Message ---
_______________________________________________ Pkg-shadow-devel mailing list [email protected] https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-shadow-devel
