Newsgroups: comp.unix.admin
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!sdd.hp.com!think.com!mintaka!bloom-picayune.mit.edu!athena.mit.edu!jik
From: jik@athena.mit.edu (Jonathan I. Kamens)
Subject: Re: Project Athena ( was Re: Non Destructive Version of rm)
Message-ID: <1991May12.230525.10111@athena.mit.edu>
Sender: news@athena.mit.edu (News system)
Organization: Massachusetts Institute of Technology
References: <12049@mentor.cc.purdue.edu> <1991May8.174603.26309@athena.mit.edu> <12067@mentor.cc.purdue.edu> <1991May9.001907.13024@athena.mit.edu> <12112@mentor.cc.purdue.edu> <1991May10.173941.8778@ariel.unm.edu> <12184@mentor.cc.purdue.edu>
Distribution: na
Date: Sun, 12 May 91 23:05:25 GMT
Lines: 16

In article <12184@mentor.cc.purdue.edu>, asg@sage.cc.purdue.edu (The Grand Master) writes:
|> Very - If I have foobar.cc.purdue.edu connected via a direct line of
|> some sort. As long as I tell my system to trus foobar ONLY when it is 
|> soming from a dedicated, hard-wired port, then all is well, and any requests
|> you make will be rejected.

  How exactly do you connect a machine to a TCP/IP network on a "direct line?"
And how exactly do the other machines on that network tell that they're
talking to the machine on the "direct line" and not to some other machine on
the same subnet?

-- 
Jonathan Kamens			              USnail:
MIT Project Athena				11 Ashford Terrace
jik@Athena.MIT.EDU				Allston, MA  02134
Office: 617-253-8085			      Home: 617-782-0710