From owner-freebsd-hackers Fri Oct 4 05:40:13 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA15766 for hackers-outgoing; Fri, 4 Oct 1996 05:40:13 -0700 (PDT) Received: from terra.Sarnoff.COM (terra.sarnoff.com [130.33.11.203]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id FAA15760 for ; Fri, 4 Oct 1996 05:40:11 -0700 (PDT) Received: (from rminnich@localhost) by terra.Sarnoff.COM (8.6.12/8.6.12) id IAA11441; Fri, 4 Oct 1996 08:39:31 -0400 Date: Fri, 4 Oct 1996 08:39:30 -0400 (EDT) From: "Ron G. Minnich" X-Sender: rminnich@terra To: Stephen Hocking cc: hackers@freebsd.org Subject: Re: SecureID cards & userland ppp In-Reply-To: <199610040739.HAA07974@netfl15a.devetir.qld.gov.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 4 Oct 1996, Stephen Hocking wrote: > My place of employment is now doing it's dialing via the SecureID stuff. For > those who don't know, each persion is issued with a nifty little card & a PIN > number. The card has a display on it that changes every 5 or so minutes. You > dial in and are prompted for a user name. Upon entering this, you are prompted > for a passcode, which is your PIN number concatenated with whatever the number > is on the display of the card at that time. As you can imagine, this makes > automating it rather difficult. One can't persuade it to prompt for user input well, if you're using chat, i had a shell script that invoked chat with the PIN after a read command. This is a problem if the dial-in sequence takes too long and the number rolls over, but in general it works well. ron