Jan Engelhardt wrote:
Is there a particular reason we still use pam_securetty.so? With `systemd-nspawn -b`, one needs an entry for "console", with `machinectl login`, somehow allowing pts/* as well. The same probably goes for kmscon.
Am I understanding that 'PAM' has also been replaced by systemd? besides console, the /etc/securetty file I have has /dev/ttyS[01] vc/[1-6] (and the pts's). What's machinectl? Would it be used to add the above? Any reason why it wouldn't just read the /etc/securetty file and apply permissions dynamically, based on user patterns, criteria and devices present in /dev? I see it used in /etc/pam.d/remote as well as /etc/pam.d/rlogin. rlogin is clear, but what progs use 'remote'? FWIW -- I've found 'rlogin' to be about 3-5X faster than ssh (over a closed/internal network). Similarly, the recently deprecated MD4 algorithm was noticeable faster than other options. Would be nice if 'ssh' had an option for using null encryption on local->local sessions. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org