FTP: Free file transfer
A 1973 proposal that FTP servers let anyone fetch publicly marked files without a user name and password.
Bressler, R.D., "Free file transfer", RFC 487, DOI 10.17487/RFC0487, April 1973, <https://www.rfc-editor.org/info/rfc487>.
@misc{rfc487,
series = {Request for Comments},
number = 487,
howpublished = {RFC 487},
publisher = {RFC Editor},
doi = {10.17487/RFC0487},
url = {https://www.rfc-editor.org/info/rfc487},
author = {R.D. Bressler},
title = {{Free file transfer}},
pagetotal = 2,
year = 1973,
month = apr,
} RFC text
Network Working Group Bob Bressler
Request for Comments #487 BBN
NIC #15065 6 April 1973
Free File Transfer
In the past several months, many people have commented to me about
their difficulty in transferring files. The hang up appears to be with
systems that have some flavor of security, but on which the user has no
access privileges. Specifically, the FTP server demands a user and
password before it will grant any system access. The loophole which
people have been using is the MAIL FILE facility, which is both limited
in scope and intended for other purposes.
A frequently used model for file protection is to define three
levels of user access: 1) only the user himself; 2) all users in a
group; 3) everyone. Up until now, "everyone" has meant anyone already
granted logon privileges. A new class is, perhaps, needed to cover
everyone, exclusive of whether or not they are logged on.
With all this in mind, I propose the following course of action:
If a user connects to an FTP server and makes a file request without
supplying a user name-password, the server should then examine the file
access parameters. If the file is listed as accessible to anyone, then
the transfer should be allowed to proceed.
This scheme can be implemented so as not to yield file creations
privileges - for example, store commands can be implemented via an
append mechanism. If I wanted a file sent to me I could create an empty
file with unlimited append access. I would then inform the foreign user
to store (append?) to that file.
The problem of accounting is somewhat more complex. Clearly,
storing a file in a user's directory can be charged to that user. When
retrieving a file from a general system directory, there is no "user"
specified, and overhead may have to be billed. The former case involved
both CPU time for transfer and secondary storage charges for storing the
new file. In the latter case, only CPU charges are involved, and these
may be sufficiently small to not cause a major problem.
BBN TENEX has agreed to modify their FTP server to allow general
access transfers as described above. Specific details for usage will be
available when installation is complete. I urge other systems to make
this service available, if only on an experimental basis. The success
of such an experiment will be judged by the reaction of the general user
community and the uses to which FTP is put.
NOTE: Bob Clements tells me that the BBN TENEX implementation will
probably require a user name of something like "FREE" or
"ANONYMOUS", but not require a password.
RB/jm
[ 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. 9/99 ]
AI ELI5
On this page
§1The Problem with Passwords
Bob Bressler of BBN reports that many people had trouble transferring files. The trouble was with systems that have some flavor of security but on which the user has no access privileges. The FTP server demanded a user name and password before it granted any system access.
The workaround people used was the MAIL FILE facility, which the RFC calls both limited in scope and intended for other purposes.
Imagine a library that makes you show a card even to read a poster on the wall. People started slipping posters through the mail slot instead.
§2The Proposal
A common file protection model has three levels: only the user, all users in a group, or everyone. Until then, everyone had meant anyone already allowed to log on. The RFC suggests a new class that covers everyone, whether or not they are logged on.
Under the proposal, a user who connects to an FTP server and makes a file request without a name and password causes the server to examine the file access parameters. If the file is accessible to anyone, the transfer should be allowed to proceed.
The scheme need not give file creation privileges. Store commands could work through an append mechanism: to receive a file, a person creates an empty file with unlimited append access and tells the sender to store to it.
Files get a new label, open to everybody. If a file has that label, the server hands it over without asking for a password.
§3Accounting and Rollout
The RFC notes that accounting is more complex. Storing a file in a user's directory can be charged to that user, covering CPU time and secondary storage. Retrieving a file from a general system directory has no user to charge, so overhead may have to be billed, but only CPU charges are involved and they may be small.
BBN TENEX agreed to modify its FTP server. A note adds that the TENEX implementation will probably require a user name such as FREE or ANONYMOUS but no password. The author urged other systems to offer the service, if only experimentally, and said success would be judged by the reaction of users and the uses made of FTP.
Someone has to pay for the electricity when guests borrow files. The author thinks the cost is small and wants to try it and see.