RFC 697 UNKNOWN FTP · SECURITY

CWD command of FTP

Two proposed ways to give FTP users access to TENEX files-only directories.

On rfc-editor.org ↗
PUBLISHED
July 1975
AUTHORS
J. Lieb
STREAM
Legacy
EXISTING CWD COMMAND
Changes working directory without granting owner access
PROPOSED CWD ARGUMENT
Optional directory password
DOI
10.17487/RFC0697

RFC text

Contents
Original text · RFC Editor View on rfc-editor.org ↗
Network Working Group                                      Jim Lieb
RFC # 697                                                  SUMEX-AIM
NIC # 32963                                                July 14, 1975


                           CWD Command of FTP


Introduction

The Tenex file system support a "files only" directory.  This type of
directory cannot be "logged in" but it can be "connected to".  A login
gives directory "owner" access to the job generated by the system and an
address space in which the user can execute programs.   A connect allows
an existing job and its associated user "owner" access to a directory
but creates no address space.  The words "owner", "group", and
"universal" or "public" determine which field of the protection
specification is to be used to check the legality of a file access
request.


Problem

The Tenex FTP server does not allow an FTP Login to a "files only"
directory.  The current protocol contains the CWD (Change Working
Directory) command which gets part of the "connect" functions but it
does not grant "owner" access to the user.  Therefore, there is no way a
user can access a "files only" directory as the "owner" (i.e. he can
supply the password).  This is undesirable for private directories of
this type since it is uneconomical to define a user - directory "group"
for so few directories and unrestricted "public" access may be
undesirable.


Solution

There are two approach we can take.  Either we remove the distinction
"files only" from the FTP login, or we create a command that does the
"connect" function.  The restriction placed on "files only" directories
is based on how we define a user of FTP to the server.  If we say that
any net user who knows the password to a directory has ownership of that
directory as far as FTP is concerned, then we have a solution.  If we
want an FTP login to be as restrictive as a user login, then we need the
second alternative.

Proposal

Change the protocol in one of the following ways:

1.  Remove the restriction on "files only" directories for FTP logins or

2.  Add an optional argument to the CWD (Change Working Directory)
    command to specify the password string for the directory.  If the
    password check is successful the user is granted ownership rights to
    that directory.  If the password is not present or the check fails,
    the command functions as it presently does and access is controlled
    by the current protection mechanism.  Anonymous users should not be
    allowed to use this mechanism to change their access to the file
    system.











       [ This RFC was put into machine readable form for entry ]
       [ into the online RFC archives by Alex McKenzie with    ]
       [ support from GTE, formerly BBN Corp.            10/99 ]

ISO Plain Language

On this page
PROBLEMTENEX's FTP server does not allow an FTP login to a files-only directory, and CWD alone does not give a user owner access to that directory.
MECHANISMThe RFC proposes either removing the login restriction for files-only directories or adding an optional directory password to the CWD command.
THE DESIGN CHOICEThe note presents alternatives for discussion and says anonymous users should not be allowed to use the password mechanism to change their access.

§1TENEX Files-Only Directories

TENEX distinguishes logging in to a directory from connecting to one. A login gives the directory owner access to a job and an address space; a connection gives an existing job access to the directory without creating an address space.

The TENEX FTP server does not allow an FTP login to a files-only directory. Its existing CWD command provides part of the connect function but does not give the user owner access, so the user cannot use the directory password to obtain owner rights through the current FTP commands.

TENEX can connect a job to a files-only directory, but its FTP login does not give the user owner access there. The current CWD command does not solve that problem.

§2Two Proposed Changes

The first proposal removes the restriction that prevents FTP login to files-only directories. Under that approach, a network user who knows the directory password would count as its owner for FTP purposes.

The second proposal adds an optional password argument to CWD. If the password matches, the user receives owner rights to the directory. If it is absent or fails, CWD works as it does under the current protection mechanism.

One option allows FTP login to a files-only directory with its password. The other keeps the existing login rule and lets CWD accept a directory password.

§3Access-Control Trade-Off

The author frames the choice around how FTP should treat the relationship between a directory password and owner access. If knowing the password is enough to count as the owner in FTP, the login restriction can be removed; if FTP login should remain as restrictive as a user login, a separate connect-style command is needed.

The proposal explicitly says anonymous users should not be allowed to use the password mechanism to change their access to the file system.

The choice is whether a directory password grants owner access during FTP login or only through an added CWD option. The note excludes anonymous users from that access change.