Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#63792 - Add pts/0 to /etc/securetty

Attached to Project: Arch Linux
Opened by Johannes Ernst (jernst) - Monday, 16 September 2019, 17:13 GMT
Last edited by Andreas Radke (AndyRTR) - Wednesday, 11 December 2019, 07:23 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Recently (not sure when exactly) systemd-nspawn has started using /dev/pts/0 as the console of the container. (I think it used to be /dev/console.) Due to this change, root login on the console of the container has become impossible -- which is a problem because there may not be any other users defined in a container.

Error message:

pam_securetty(login:auth): access denied: tty 'pts/0' is not secure !

To make it possible again, pts/0 needs to be added to /etc/securetty.

This task depends upon

Closed by  Andreas Radke (AndyRTR)
Wednesday, 11 December 2019, 07:23 GMT
Reason for closing:  Duplicate
Additional comments about closing:  FS#45903
Comment by nl6720 (nl6720) - Monday, 16 September 2019, 17:32 GMT
Possible duplicate of FS#45903 ?

See also https://github.com/systemd/systemd/issues/852 .
Comment by Johannes Ernst (jernst) - Monday, 16 September 2019, 17:48 GMT
I don't know how this is supposed to work, and because of that I'm not sure whose resposibility it is to fix this how. I only know it used to work and it doesn't any more :-)

So I also filed a bug against systemd: https://github.com/systemd/systemd/issues/13532 in the hope that somebody in either project knows how it is supposed to work and either accepts or closes either bug on either side.

I don't think it is directly related to something that happened in 2015 because this problem only started occurring some time in the past few months.

Loading...