Документ взят из кэша поисковой машины. Адрес оригинального документа : http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/pdfrfc/rfc487.txt.pdf Дата изменения: Wed Mar 27 23:47:24 2002 Дата индексирования: Tue Oct 2 16:27:47 2012 Кодировка:

Network Working Group Request for Comments #487 NIC #15065

Bob Bressler BBN 6 April 1973

Free File Transfer

In the past several months, many people have their difficulty in transferring files. The hang systems that have some flavor of security, but on access privileges. Specifically, the FTP server password before it will grant any system access. people have been using is the MAIL FILE facility, in scope and intended for other purposes.

commented to me about up appears to be with which the user has no demands a user and The loophole which which is both limited

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 privileges - for example, store commands can be append mechanism. If I wanted a file sent to me file with unlimited append access. I would then to store (append?) to that file. yield file creations implemented via an I could create an empty inform the foreign user

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

Bressler

[Page 1]


RFC 487

Free File Transfer

April 1973

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 ]

Bressler

[Page 2]