Hello, recently I've encoutered problems logging into my systems with network detached. After some investigations I've found lookups of ttyX.mydomain trying to reach my DNS servers and timing out before successful login. Today I've located the source of such weird behaviour: /etc/security/access.conf + : root : tty1 tty2 tty3 tty4 tty5 tty6 tty7 tty8 However digging on pam-list resulted in some hints: https://www.redhat.com/archives/pam-list/2007-December/msg00018.html https://www.redhat.com/archives/pam-list/2007-December/msg00018.html In fact there is something related in login-utils/login.c:555 /* hostname & tty are either set to NULL or their correct values, depending on how much we know */ retcode = pam_set_item(pamh, PAM_RHOST, hostname); PAM_FAIL_CHECK; retcode = pam_set_item(pamh, PAM_TTY, tty_name); PAM_FAIL_CHECK; I suspect this can be related to my symptoms. And the question is: is this the way it SHOULD work? It's pointless to check local tty names in DNS and dangerous in terms of delaying local system access without network. -- Tomasz Pala <gotar@xxxxxxxxxxxxx> -- To unsubscribe from this list: send the line "unsubscribe util-linux-ng" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
