Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!cornell!batcomputer!itsgw!steinmetz!uunet!ateng!chip From: chip@ateng.ateng.com (Chip Salzenberg) Newsgroups: comp.mail.uucp Subject: Re: problems with att multiple-machine approach? Message-ID: <1988Oct3.115720.2175@ateng.ateng.com> Date: 3 Oct 88 15:57:19 GMT References: <1988Sep23.105347.652@lsuc.uucp> <2300@att.ATT.COM> <1988Sep29.210829.29073@lsuc.uucp> Organization: A T Engineering, Tampa, FL Lines: 20 According to dave@lsuc.uucp (David Sherman): >> [att does] not trust that a machine calling in is actually who it says it >> is. It is a trivial command to change a machine's nodename... >> So, except in rare cases, we only deliver mail when >> we make the call. > >Uh, yeah. Not to get snarky or anything, but many years ago >someone came up with this wonderful idea called a PASSWORD. >Just give each machine its own login. ...which solves nothing. If I (ateng) have a UUCP login on att, then I can change my nodename to uunet and then use the 'ateng' login. Presto, I've logged in successfully and picked up uunet's mail. This does leave tracks in the log files; but the damage is done by the time it's discovered. -- Chip Salzenberg or A T Engineering Me? Speak for my company? Surely you jest! >> Beware of programmers carrying screwdrivers. <<