X-Organization: Penn State University / University Libraries
X-Envelope-to: novell@suvm.BITNET
X-VMS-To: NOVELL_L
Newsgroups: bit.listserv.novell
Date:         Tue, 17 Nov 1992 12:10:00 EST
Reply-To:     Novell LAN Interest Group <NOVELL@SUVM.BITNET>
From:         "J.Lance Wilkinson, 814-865-1818" <JLW@PSULIAS.BITNET>
Subject:      Looking for .BAT file INPUT of password...

Given the recent spate of discussion concerning various ways to pump a password
into a login and/or attach command, I was wondering if anyone has any
suggestions on a way I'd like to use it:

We have a PC workstation, files stripped down to just those necessary for
basic PC-DOS 5.0, Novell and our backup software.  We use it to back up the
files on the servers.  The autoexec currently invokes login to log onto the
primary server, then attach for each of the other servers.  The same id is
used on all servers, with the same password.  The id is fixed, and as such can
be (and *is*) hardcoded in the autoexec sequence.  The password, while the
same for the id on all servers, must be typed in in response to the password:
prompts.  The use of various tools (I like the echo <password>|<command> method
since it doesn't require anything beyond DOS) allow me to can the password,
but I'd rather that when the station is booted, its operator have to type in
the password -- ONCE.

So far I've determined that if the login and attaches are in a batch file,
I can do it this way:

        echo off
        echo %1|login primary/backemup
        echo %1|attach scndry1/backemup
        echo %1|attach scndry2/backemup
        echo %1|attach scndry3/backemup
        echo off

This means the user need only type in the password once, and the autoexec
can then pass that password as the single argument to the login/attach batch
file.  But I can't find any primatives in DOS 5.0 that will allow me to have
the autoexec *PROMPT* for that one type password.  I don't want any judgement
calls on the part of the operator -- they simply need to turn on the machine,
wait for the prompt and type their password, much in the same way as the PC
could (probably should) have a poweron password.  I don't want the password
recorded in a file anywhere, both for security's sake and for the fact that
the password lifetime is limited and must be changed periodically (no editing
of a "password" file, please!).

Suggestions for PD code?  I've considered DOS 5.0's DOSKEY, but symptoms in the
past suggested that any TSRs might mess up the backup software, and that
includes DOSKEY of course.

+-"Never Underestimate the bandwidth of a station wagon full of mag tapes"--+
| J.Lance Wilkinson ("Lance")            BitNet:    JLW@PSULIAS.BITNET      |
| Systems Design Specialist - Lead       InterNet:  JLW@PSULIAS.PSU.EDU     |
| Library Computing Services         AT&T:(814) 865-1818 FAX:(814)863-3560  |
| E8 Pattee Library                      "I'd rather be dancing..."         |
| Penn State University         A host is a host from coast to coast,       |
| University Park, PA 16802     And no one will talk to a host that's close |
| <POSTMAST@PSULIAS.BITNET>     Unless the host that isn't close            |
| <POSTMAST@PSUCES.BITNET>      Is busy, hung or dead.                      |
+------"He's dead, Jim. I'll get his tricorder. You take his wallet."-------+