Firstly, thanks to all who responed. I got so many answers I felt like
a Florida ballot counter. (American joke). I got many answers some
easy to implement, others more involved. I went with one of the easy
ones for immediate effect but I would like to look at some of the more
complex ones.
Lawrie Smith, Chris Bryant, Robert Sloane and Charles Ballowe gave
similar simple answers along the following lines.
set the user shell to /bin/false in the /etc/passwd file and make sure
/bin/false is in the /etc/shells file
also put /usr/bin/ftp in the /etc/shells file and then make /usr/bin/ftp
the shell for that user account
These were extremely simple and as this is a one time deal while we
determine why the customer is unable to use the secure ftp from behind
the firewall.
One other simple one from Darryl Cook was to look into the ftpaccess man
page and check the restricted uid section. He said this appears to
restrict a uid to its home directory when that uid is added to the
restricted uid section.
Dennis Peacock suggested a user account with a shell set to /bin/false
and a locked passwd. This looks pretty straightforward too.
Others suggested wu_ftp, ncftpd, ftp servers, anonymous ftp, profitpd.
Sorry I did not list all names but I had quite a few replies.
On Thu, 31 Jan 2002, Smith, Mike R. wrote:
> I have a request to set up an account for a customer. They will ftp
> some files in on a regular basis but they do not need to go anywhere
> else on the system. I found notes on the Rsh shell which seemed like
> what I wanted except it does not allow ftp access. Can anyone point me
> to the right way to do this.
Received on Thu Jan 31 2002 - 20:03:21 NZDT