Coda File System

Automated clog in login scripts

From: Jason A. Pattie <pattieja_at_pcxperience.com>
Date: Mon, 23 Feb 2004 15:28:30 -0600
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

What would it take to setup .login or .bash_login or .bashrc, etc. to
automatically detect that a user logging in has or does not have a token
and then prompt them for a token authentication (via clog)?  I'm
thinking I would need to grep against the output of ctokens for all the
different possibilities to determine that this user does or does not
have a valid token, etc., and then continue to login or run clog to have
them enter their passphrase to obtain a valid token.  I will also need
to know whether they are starting in disconnected mode or not to be able
to determine (based on hostname, I would assume) if I pull an
authentication token using '-fromfile' or automatically use '-tofile'.

I am aware of the Kerberos/PAM interface but don't want to go there at
this time.

Thanks.

- --
Jason A. Pattie
pattieja_at_xperienceinc.com
Xperience, Inc. (http://www.xperienceinc.com)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
Comment: Using GnuPG with Debian - http://enigmail.mozdev.org

iD8DBQFAOnB+uYsUrHkpYtARAkFPAJ4oIRCxDC+6OP7e9eiqogUtQjTNeQCcDjIO
ot1dBL4JDvtn8u/6Ty/y+T0=
=AMMB
-----END PGP SIGNATURE-----


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
MailScanner thanks transtec Computers for their support.
Received on 2004-02-23 16:29:56