oops, yes, my bad.
On Thu, Mar 27, 2008 at 3:48 PM, J.L.H.W. Linkels <[EMAIL PROTECTED]> wrote: > Do you mean in the file /etc/pam.d/ssh? > > Hans > > > > > On Thursday 27 March 2008 15:42, Georges A.K. wrote: > > You'll have to disable common-auth in /etc/pam.d and manually enter > > the authentications you want, for example: > > auth required pam_env.so > > auth required pam_unix2.so > > > > I had already done it and it worked. > > > > Georges. > > > > On Thu, Mar 27, 2008 at 11:48 AM, J.L.H.W. Linkels <[EMAIL PROTECTED]> > wrote: > > > Hello all, > > > > > > fprint works great otherwise, but when I am logged in remotely thru SSH > > > and want to become root, PAM asks for a fingerprint scan. I only can > > > fulfill that request by going over to the laptop and swipe my finger. > > > > > > Logging in remotely thru SSH is apparently detected and possible, no > > > finger print asked. Obviously logging in as root remotely is disabled, so > > > I must log in as user first and then do 'su'. > > > > > > I am sure this is not so much a bug in fprint as something which has to > > > be configured. But how can you configure that 'su' must not use fprint > > > authentication when you are connected remotely? How can PAM detect that > > > you ssh in instead of using an xterm? And once this is detected, how do > > > you exclude fprint authentication? I found ways to include authentication > > > in the various /etc/pam.d file, but not how to exclude something. In each > > > file 'common-auth' is included, but 'common-auth' contains the line which > > > enables pam_fprint. > > > > > > Thanks > > > jlinkels > > > > > > _______________________________________________ > > > fprint mailing list > > > [email protected] > > > http://lists.reactivated.net/mailman/listinfo/fprint > _______________________________________________ fprint mailing list [email protected] http://lists.reactivated.net/mailman/listinfo/fprint
