home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!sdd.hp.com!usc!sol.ctr.columbia.edu!emory!ogicse!das-news.harvard.edu!spdcc!dyer
- From: dyer@spdcc.com (Steve Dyer)
- Newsgroups: comp.protocols.tcp-ip
- Subject: Re: How to control permissions on incoming FTP?
- Message-ID: <1992Jul30.070925.23754@spdcc.com>
- Date: 30 Jul 92 07:09:25 GMT
- References: <51690@drilex.dri.mgh.com> <1582elINN9mf@early-bird.think.com>
- Organization: S.P. Dyer Computer Consulting, Cambridge MA
- Lines: 28
-
- In article <1582elINN9mf@early-bird.think.com> barmar@think.com (Barry Margolin) writes:
- >Others have already suggested getting public ftpd source and adding a
- >umask() call.
- >
- >Another solution is to run ftpd via a script that first sets the umask and
- >then execs the real ftpd. I believe the standard BSD telnet just inherits
- >its umask from its parent.
-
- That's fine, but it affects all incoming FTP tasks. Some of your
- users might not like such a decision being made for them. I wanted
- a version of anonymous FTP which allowed deposition of files into
- a writable 'incoming' directory, but the resulting files would not
- be generally accessible to anonymous FTP browsers. I didn't want
- to affect anyone other users of ftp.
-
- Until I made the (simple) change to ftpd, I maintained a writable
- directory accessible via anonymous FTP. One day I was amused (surprised
- is too strong a word) to discover that said directory was being used as
- a world-wide rendezvous point for porno GIF seekers and providers: there
- was even a convention for creating hidden directories in the incoming
- directory, one for requests and one for replies. Files named like
- I_want_wandanude.gif in the requests directory would cause wandanude.gif
- to appear in the reply directory, and so on. Ingenious, but not on
- my bandwidth...
-
- --
- Steve Dyer
- dyer@ursa-major.spdcc.com aka {ima,harvard,rayssd,linus,m2c}!spdcc!dyer
-