Path: utzoo!lsuc!ncrcan!ziebmef!cks From: cks@ziebmef.uucp (Chris Siebenmann) Newsgroups: unix-pc.general Subject: Re: UNIXPC uucp problem Message-ID: <1988Jul4.173733.7088@ziebmef.uucp> Date: 4 Jul 88 21:37:32 GMT References: <1988Jun27.202651.9458@ziebmef.uucp> <103@cjsa.UUCP> Reply-To: cks@ziebmef.UUCP (Chris Siebenmann) Organization: Ziebmef Public Access BBS/Unix Lines: 24 In article <103@cjsa.UUCP> jeff@cjsa.UUCP (C. Jeffery Small) writes: ... >I had this very problem when I first set up USENET software. I believe >the problem has to do with the way uucp, nuucp, etc. entries appear and >are parsed in the passwd file. I believe that your problem will go away >(and your security increased) if you make seperate password entries with >unique uids for each machine that you wish to allow to dial in. Actually, all uucp dialins have to share the same UID as 'uucp'. If they don't, connections fail with a very obscure error message (I believe 'BAD LOGIN/MACHINE NAME' again) -- I got bitten by this when I first set up the uucp logins on ziebmef. In hindsight, this makes sense; it means that people can't just invoke uucico from their own accounts and pretend to be some random machine. Instead you somehow have to set your uid to the 'uucp' UID. Could have been worse, I suppose; they could have hardcoded the uucp UID into uucico instead of looking it up in /etc/passwd. -- You're a prisoner of the dark sky/The propeller blades are still And the evil eye of the hurricane's/Coming in for the kill Chris Siebenmann uunet!utgpu!{ontmoh!moore,ncrcan}!ziebmef!cks cks@ziebmef.UUCP or .....!utgpu!{,ontmoh!,ncrcan!brambo!}cks