Technical article 111093

I followed the instructions in SCOhelp for creating an anonymous ftp account but the ftp user isn't restricted to the ftp directory.

OpenServer 5.0.0OpenServer 5.0.2OpenServer 5.0.4OpenServer 5.0.5

Written · Last revised

Problem

I created an anonymous ftp account per the instructions in SCOhelp under the SCO OpenServer 5.x Networking Guide. Step 3 states the following:

3. Create a symbolic link to the ftp home directory as follows:

ln -s <homedir> /usr/internet/ip/0.0.0.0/sco_ftp

where <homedir> is the location of the home directory you specified when creating the ftp account.

The command results in this message:
                ln: cannot create symbolic link
/usr/internet/ip/0.0.0.0/sco_ftp: No
                such file or directory (error 2)
The /usr/internet/ip/0.0.0.0 directory does not exist.  I then
created the 0.0.0.0 directory:
cd /usr/internet/ip
mkdir 0.0.0.0

I was then successful at executing the link command in step 3.

Following the rest of the instructions, I was able to successfully create the anonymous ftp account and to ftp in from a remote system. However, I can change directory (cd) to any directory on the system. As an anonymous ftp user, I should be restricted from moving outside my created directory tree.

Cause

There is no instruction for setting the ftp account as restricted
in step 2.  Step 2 currently reads:

2. Create a user called ftp with the Account Manager. Do not set the password when creating the user.

Solution

To work around this, replace step 2 with the following:

2. Create a user called ftp with the Account Manager. Change the shell for the ftp user from "sh" to "rsh". rsh is a restricted shell. Do not set the password when creating the user.

This problem has been reported to SCO Engineering.

From the Xinuos technical article database, record 111093. Reproduced with permission. The original is at www.sco.com/ta/111093, which is reachable but blocked from search engines. Xinuos marks this article against a retired product line. That refers to the product’s lifecycle, not to whether the advice still works — plenty of it still applies to running systems.

Next step

Need this fixed rather than explained?

Tell us the release, what the system runs and what it is doing. We will reply by email with what we would do next.

  • You deal with the people who do the work
  • No obligation, and no upgrade required before we will help
  • We tell you plainly if something is not worth doing

Send an enquiry

We reply by email. If a server is down, say so in the first line. You can also write to help@scoexpert.com.