Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!olivea!samsung!caen!gilgalad
From: gilgalad@caen.engin.umich.edu (Ralph Seguin)
Newsgroups: comp.sys.next
Subject: Re: SLIP from next.com
Message-ID: <1991Feb19.231809.24359@engin.umich.edu>
Date: 19 Feb 91 23:18:09 GMT
References: <5240@media-lab.MEDIA.MIT.EDU> <3191@unccvax.uncc.edu>
Sender: news@engin.umich.edu (CAEN Netnews)
Organization: University of Michigan Engineering, Ann Arbor
Lines: 33

In article <3191@unccvax.uncc.edu> cbenda@unccvax.uncc.edu (carl m benda) writes:
>In article <5240@media-lab.MEDIA.MIT.EDU>, lacsap@plethora.media.mit.edu (Pascal Chesnais) writes:
>> To clarify matters of where I am coming from-
>> 
>> Next does not publically list any of its machines as anonymous
>> ftp archive servers for the internet.  If they have a security
>> hole, I do not exploit it even though I know it exists.

>> pasc

Is this not the same thing as restricting access to some set of individuals.
You CAN specify who gets FTP access to a machine.  But, the rule goes:
If it's anonymous FTP, then you had better be prepared to accept the consequences.

>Not to start a flame war, but... you of all people comming from RMS land
>up @ mit should realize the difference between publicly listing a machine
>versus simply leaving a machine open for access.  I.E. you don't announce
>to the world that you are leaving your newspaper on the subway for someone
>else to use when you get off at your stop, nevertheless, the newspaper IS
>available to the public...  If I were looking for good quality public domain
>NeXT machine source code, blah_blah_.next.com is probably the first place I
>would try.  IF I'm wrong, let me know, but I always thought that if its
>"getable" its public.

I agree with this.

>/Carl



Ralph Seguin			gilgalad@dip.eecs.umich.edu
536 South Forest Apt. #915	gilgalad@caen.engin.umich.edu
Ann Arbor, MI 48104		(313) 662-4805