Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!bellcore!petrus!scherzo!allegra!mit-eddie!think!harvard!seismo!rochester!rocksanne!sunybcs!kitty!larry
From: larry@kitty.UUCP (Larry Lippman)
Newsgroups: net.bugs.uucp,net.bugs.usg,net.unix,net.unix-wizards
Subject: Re: Re: UUCP from 4.2BSD->AT&T 3B2
Message-ID: <730@kitty.UUCP>
Date: Sun, 19-Jan-86 23:31:44 EST
Article-I.D.: kitty.730
Posted: Sun Jan 19 23:31:44 1986
Date-Received: Thu, 23-Jan-86 21:36:56 EST
References: <1519@sphinx.UChicago.UUCP> <3171@sun.uucp>
Organization: Recognition Research Corp., Clarence, NY
Lines: 39
Xref: watmath net.bugs.uucp:675 net.bugs.usg:425 net.unix:6902 net.unix-wizards:16486

> > I am attempting to establish a UUCP connection between my Pyramid and a
> > AT&T 3B2-400.  When we call the 3B2, uucico fires up on their side and
> > identifies their system properly.  It then sends LOGIN where my system is
> > expecting OK.
> 
> See reply to other similar reported problem.  It has nothing whatsoever to
> do with the UUCP running on the calling side; it could be anything from V7
> to System V Release 2, and probably even Honey Danber, and the same problem
> would occur.  The problem is that the *called* side hasn't had its USERFILE
> (or the Honey Danber equivalents) set up right; System V Release 2's UUCP
> enforces rules that had never been enforced before, and which people got
> used to not being enforced.  You *must* enable logins for *every* account
> used by UUCP in the USERFILE or whatever file(s) Honey Danber uses.
                                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

	Generally /usr/lib/uucp/Permissions is the file name.  Some of the
uucp logfile errors resulting from incorrect entries in the above file are:
"HANDSHAKE FAILED" and "REMOTE REJECT AFTER LOGIN".  If you have Honey Danber,
chances are you have a program called /usr/lib/uucp/uucheck which facilitates
checking the correctness of Permissions file entries.
	I would also suggest the following to simplify uucp troubleshooting
and to improve system security:

1.	Create (in /etc/passwd) individual uucp logins for EACH remote system;
	e.g., `uusysx', `uusysy', etc. and block the general entries for
	`uucp' and `nuucp'.  This also gives you additional information for
	your accounting program, if you run one.

2.	Create individual entries for each remote system in the Permissions
	file, with each entry being in the combined machine/logname format.

3.	Disable the "remote.unknown" option.

==>  Larry Lippman @ Recognition Research Corp., Clarence, New York        <==
==>  UUCP    {decvax|dual|rocksanne|rocksvax|watmath}!sunybcs!kitty!larry  <==
==>  VOICE   716/741-9185                {rice|shell}!baylor!/             <==
==>  FAX     716/741-9635 {G1, G2, G3 modes}    duke!ethos!/               <==
==>                                               seismo!/                 <==
==>  "Have you hugged your cat today?"           ihnp4!/                   <==