I've been looking at skey, one-time pads, etc. One issue which doesn't
seem to be addressed is the mixing of authentication types. For example,
inside a reasonably secure net one might chose to use `ordinary' unix
authentication. When accessing from outside, one might want to normally
use skey, but fall back to a set of memorized one-time passwords if no
local/trustworthy skey generator is available.
The trick is how to decide on the fly which to use. Alternate ports for
alternate authentications involves excessive memorization. What I'd do
if I were recoding login.c is to let one modify the login id to indicate
desired authentication type:
login: scs # system default
login: scs/skey # skey
login: scs/onetime # one-time list
login: scs/unix # normal unix
login: scs/whatever # local custom job
A good implementation would refuse to do the wrong thing, eg, not permit
scs/unix from locations known to be outside the secured facility. If
anybody's thought seriously about the virtues of this or has other
solutions, I'd love to hear it.
|
|
