Path: utzoo!utgpu!utstat!jarvis.csri.toronto.edu!mailrus!cornell!rochester!rutgers!att!chinet!les
From: les@chinet.chi.il.us (Leslie Mikesell)
Newsgroups: comp.mail.uucp
Subject: Re: The login: prompt.
Message-ID: <7923@chinet.chi.il.us>
Date: 12 Mar 89 22:39:50 GMT
References: <0724.AA0724@julie>
Reply-To: les@chinet.chi.il.us (Leslie Mikesell)
Organization: Chinet - Public Access Unix
Lines: 35

In article <0724.AA0724@julie> mcr@julie.UUCP (Michael Richardson) writes:

>  I am in the process of writing a "Front Door/Sea Dog/Binkley"-like
>program (for the Amiga of course) that sits in front of a bbs and does mail
[..]
>  I've done enough uucp connection configuring (but never with HDB uucp,
>only BSD or mickey mouse micro uucp stuff.) to realise that most
>system administrators already know how to do "ogin:" <name> "sword:" <password>"
>stuff, but is there any real reason that this has to be done?

The uucp login script is really in the form of:
expect send expect send
with the variation that:
expect1-senda-expect2
means that if the expect1 sequence is not received within the timeout
interval, then send "senda" with an implicit carriage return and then
wait for the expect2 sequence.  The alternate sequences can be nested
and a null expect "" may be used if the caller should send something
before expecting anything back.

>  I don't want to put up a "login:" prompt and then look for sync's
>or login names, confusing the heck out of human callers when they have to
>enter "bbs" or they enter their name and then I pull the bbs (or whatever---
>I'm not specific) up. I don't to have anything to do with "user logs" or
>passwd files.

The point of this is that you should output whetever you want your
human callers to see (as does unix with the "login:" prompt) and make
the script look for that.  You are obviously going to have to keep
track of the system names somewhere in order to know which files to
send so you might as well do it based on the login name and use a
password if you want security.  That way you can also use alternate
protocols for different sites.

Les Mikesell