Embed Doc
Copy Link
Readcast
Collections

CommentGo Back

Download

Network Working Group T. YlonenInternet-Draft S. LehtinenExpires: April 1, 2002 SSH Communications Security CorpOctober 2001SSH File Transfer Protocoldraft-ietf-secsh-filexfer-02.txtStatus of this MemoThis document is an Internet-Draft and is in full conformance withall provisions of Section 10 of RFC2026.Internet-Drafts are working documents of the Internet EngineeringTask Force (IETF), its areas, and its working groups. Note thatother groups may also distribute working documents as Internet-Drafts.Internet-Drafts are draft documents valid for a maximum of six monthsand may be updated, replaced, or obsoleted by other documents at anytime. It is inappropriate to use Internet-Drafts as referencematerial or to cite them other than as "work in progress."The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt.The list of Internet-Draft Shadow Directories can be accessed athttp://www.ietf.org/shadow.html.This Internet-Draft will expire on April 1, 2002.Copyright NoticeCopyright (C) The Internet Society (2001). All Rights Reserved.AbstractThe SSH File Transfer Protocol provides secure file transferfunctionality over any reliable data stream. It is the standard filetransfer protocol for use with the SSH2 protocol. This documentdescribes the file transfer protocol and its interface to the SSH2protocol suite.Ylonen & Lehtinen Expires April 1, 2002 [Page 1]Internet-Draft SSH File Transfer Protocol October 2001

Table of Contents1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 32. Use with the SSH Connection Protocol . . . . . . . . . . . . 43. General Packet Format . . . . . . . . . . . . . . . . . . . 54. Protocol Initialization . . . . . . . . . . . . . . . . . . 75. File Attributes . . . . . . . . . . . . . . . . . . . . . . 86. Requests From the Client to the Server . . . . . . . . . . . 106.1 Request Synchronization and Reordering . . . . . . . . . . . 106.2 File Names . . . . . . . . . . . . . . . . . . . . . . . . . 116.3 Opening, Creating, and Closing Files . . . . . . . . . . . . 116.4 Reading and Writing . . . . . . . . . . . . . . . . . . . . 136.5 Removing and Renaming Files . . . . . . . . . . . . . . . . 146.6 Creating and Deleting Directories . . . . . . . . . . . . . 156.7 Scanning Directories . . . . . . . . . . . . . . . . . . . . 156.8 Retrieving File Attributes . . . . . . . . . . . . . . . . . 166.9 Setting File Attributes . . . . . . . . . . . . . . . . . . 176.10 Dealing with Symbolic links . . . . . . . . . . . . . . . . 186.11 Canonicalizing the Server-Side Path Name . . . . . . . . . . 187. Responses from the Server to the Client . . . . . . . . . . 208. Vendor-Specific Extensions . . . . . . . . . . . . . . . . . 249. Security Considerations . . . . . . . . . . . . . . . . . . 2510. Changes from previous protocol versions . . . . . . . . . . 2610.1 Changes between versions 3 and 2 . . . . . . . . . . . . . . 2610.2 Changes between versions 2 and 1 . . . . . . . . . . . . . . 2610.3 Changes between versions 1 and 0 . . . . . . . . . . . . . . 2611. Trademark Issues . . . . . . . . . . . . . . . . . . . . . . 27References . . . . . . . . . . . . . . . . . . . . . . . . . 28Authors' Addresses . . . . . . . . . . . . . . . . . . . . . 28Full Copyright Statement . . . . . . . . . . . . . . . . . . 29Ylonen & Lehtinen Expires April 1, 2002 [Page 2]Internet-Draft SSH File Transfer Protocol October 2001

1. IntroductionThis protocol provides secure file transfer (and more generally filesystem access) functionality over a reliable data stream, such as achannel in the SSH2 protocol [3].This protocol is designed so that it could be used to implement asecure remote file system service, as well as a secure file transferservice.This protocol assumes that it runs over a secure channel, and thatthe server has already authenticated the user at the client end, andthat the identity of the client user is externally available to theserver implementation.In general, this protocol follows a simple request-response model.Each request and response contains a sequence number and multiplerequests may be pending simultaneously. There are a relatively largenumber of different request messages, but a small number of possibleresponse messages. Each request has one or more response messagesthat may be returned in result (e.g., a read either returns data orreports error status).The packet format descriptions in this specification follow thenotation presented in the secsh architecture draft.[3].Even though this protocol is described in the context of the SSH2protocol, this protocol is general and independent of the rest of theSSH2 protocol suite. It could be used in a number of differentapplications, such as secure file transfer over TLS RFC 2246 [1] andtransfer of management information in VPN applications.Ylonen & Lehtinen Expires April 1, 2002 [Page 3]Internet-Draft SSH File Transfer Protocol October 2001