Pam-list Digest, Vol 38, Issue 4
Andrew Morgan
morgan at kernel.org
Mon Apr 16 05:32:22 UTC 2007
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Andreas Schindler wrote:
> To the discussion about PAM_DISPLAY: Before all, please consider that
> every X-Display on a local machine (i.e. DISPLAY=x.x or localhost:x.x)
> ALWAYS has an associatet TTY, because the X-Server needs a (pseudo-)device
> to attach to. So, PAM_TTY and PAM_DISPLAY should be independent of each
> other.
Did you consider this X display?
(vncserver < /dev/null 2>&1 > /dev/null)
The use of PAM_TTY is primarily for the application to communicate to
modules where the user input/output is coming from/going to, in the case
of X, a remote display's underlying terminal (a la vncviewer) might
change at random many times during the life of a vncserver session.
Cheers
Andrew
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)
iD8DBQFGIwpMQheEq9QabfIRAttGAKCO9m+M0/AMu3h/1EsriQU0VEySHQCgiJkB
ahN09Xj03zYWLxwwRE4mJpc=
=SbnF
-----END PGP SIGNATURE-----
More information about the Pam-list
mailing list