🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.admin.policy
Article #774

Re: RFC on my "abuse"

#774
From: Paul M. Mickel
Date: Wed, 26 Jun 1991 02:32
52 lines
2967 bytes
In article <JGREELY.91Jun25172338@morganucodon.cis.ohio-state.edu> J Greely <jgreely@cis.ohio-state.edu> writes:

>In article <1991Jun25.192914.23335@cs.utk.edu> de5@ornl.gov (Dave Sill) writes:
>>Attempting to anonymous ftp to random sites is, in my opinion, rude at
>>worst.  But any site admin that freaks out over the occasional attempt
>>hasn't got a firm grasp on reality.
>
>Actually, they may have a firmer grip than you.  Older versions of
>ftpd had holes big enough to drive a truck through.  If I spotted
>someone out at bfe.edu attempting to connect to each of our machines
>in turn, I'd be more than a little suspicious, and would probably send
>mail to the admins there asking them to check it out.

[some deleted for brevity]

>
>  It sounds like the actions taken by the original sysadmins were
>quite reasonable.
>-- 
>J Greely (jgreely@cis.ohio-state.edu; osu-cis!jgreely)

In reading all of the articles on this subject, I have reached some 
conclusions:

1. That the justification for this action really depends on the site.
   As this poster pointed out, if there are some problems with security
   via anomyous ftp, then maybe the sysadmin at that site is justified
   in making a ruckus.

2. As far as I understand it, that anomyous ftp is provided as a courtesy
   to others. If only one user is causing the problem, then an email 
   request to that person is in order requesting a discontinuance of the
   action. However, this person should not lose their account for trying
   to access an ftp site that is public. If the sysadmin *really* doesn't
   like it, then maybe he should cosider removing the anomyous ftp from
   his site, but not ask for the offending user's head on a platter,
   so to speak.

I guess that the moral to this story is that the sysadmin at the anomyous
ftp site should consider his policy toward anomyous ftp, and act according-
ly. He should also remember that there are always unforseen problems 
associated with anomyous ftp and use his judgement before acting.

#include <stddisclaimer.h>



Paul M. Mickel				mickelp@prism.cs.orst.edu
Oregon State University			Corvallis, OR   97331
--------------------------------------------------------------------
"Where there's life and food, there is hope."
			- own saying
Technical Details
Message-ID: <1991Jun26.023211.4222@lynx.CS.ORST.EDU>
Path: arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!mintaka!ogicse!orstcs!prism!mickelp
References: <1991Jun25.173013.3784@mp.cs.niu.edu> <1991Jun25.192914.23335@cs.utk.edu> <JGREELY.91Jun25172338@morganucodon.cis.ohio-state.edu>

Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!mintaka!ogicse!orstcs!prism!mickelp
From: mickelp@prism.cs.orst.edu (Paul M. Mickel )
Newsgroups: comp.admin.policy
Subject: Re: RFC on my "abuse"
Message-ID: <1991Jun26.023211.4222@lynx.CS.ORST.EDU>
Date: 26 Jun 91 02:32:11 GMT
Article-I.D.: lynx.1991Jun26.023211.4222
References: <1991Jun25.173013.3784@mp.cs.niu.edu> <1991Jun25.192914.23335@cs.utk.edu> <JGREELY.91Jun25172338@morganucodon.cis.ohio-state.edu>
Sender: @lynx.CS.ORST.EDU
Distribution: usa
Organization: Oregon State University, Computer Science Dept.
Lines: 52
Nntp-Posting-Host: prism.cs.orst.edu