In comp.os.linux.networking Vin McLellan <(E-Mail Removed)>:
> GoogleMike@@hotpop.com offered a bit of overclocked hyperbole when he
> described his SecurID token:
>> I use an RSA SecurID Keyfob that spits out a new 6 digit
>> number every 10 seconds. When prompted to login (at
>> least on Windows), I take my username of "gmike" and
>> my passcode "4430" + SecurID number.
> The classic RSA SecurID continuously generates and displays a new 6-8
> digit (or alphanumeric) "token-code" every 60 seconds. As Mike noted,
> SecurIDs are always used in a "two-factor" format that requires both a
> user-memorized PIN or password, and a SecurID token-code, for a valid
> user authentication.
> Again, a SecurID LCD displays a new token-code every 60 seconds. A RSA
> customer could do a special order, I suppose -- but I can't imagine any
> circumstance in which anyone would want, or need, a SecurID that
> generates a new token-code "every 10 seconds." That's a description
> that can confuse or scare folks. Too fast for mere mortals or tcp/ip
> networks, right?
Absolutely, any card I have seen gives every 60 seconds a new
token, those are quite often used for slow dial-up/etc
connections.
You need some time to open the connection and the ace or so
server, which must not be the dial-in server or better should
not, needs some time for communication and calculating the token.
10 sec. are likely to short for all this to happen.
--
Michael Heiming (X-PGP-Sig > GPG-Key ID: EDD27B94)
mail: echo
(E-Mail Removed) | perl -pe 'y/a-z/n-za-m/'
#bofh excuse 270: Someone has messed up the kernel pointers
Similar Threads
Linear Mode
