Darren J Moffat wrote:
> I think this project should NOT be introducing multi-threaded PAM
> module, or expecting PAM applications to be multi-threaded nor should it
> be trying to do things with the X input model. I believe that this case
> should following the existing architecture that is used for smartcard
> support via PAM and the login applications. That likely means that the
> currently private (and marked obsolete) message types below should be
> formalised and made Committed - assuming the solve the same problem for
> fingerprint readers that they do for smartcard.
>
> #define PAM_MSG_NOCONF 2001 /* No confirmation from user */
> #define PAM_CONV_INTERRUPT 2002 /* Return from conv() */
I thought smartcard abandoned those as well? We don't support either
one in xscreensaver in Nevada. (They were removed when the direct
calls to the SCF/OCF smartcard framework were removed.)
--
-Alan Coopersmith- alan.coopersmith at sun.com
Sun Microsystems, Inc. - X Window System Engineering
