SFTP specifications: Difference between revisions

From FileZilla Wiki
Jump to navigationJump to search
(Revert spam)
(Undo revision 9342 by Pranavwright (talk))
Line 1: Line 1:
The ''SSH File Transfer Protocol'' (SFTP) is used to transfer files over a cryptographically protected ''Secure Shell'' (SSH) connection.
,  In a universe of aponicatipls, including both latency-sensitive and insensitive aponicatipls, it is difficult to regard the IP suite as truly neutral. TCP/IP is so non-neutral that it was necessary to invent UDP/IP at the same time. And these two transports don't encompass all possible network application paradigms.So no, the TCP/IP protocol stack is not application-neutral in any meaningful sense of the word.You may as well be arguing that the poll tax was not discriminatory because it applied to everyone, rich and poor alike.
 
== Technical Specifications ==
 
=== SSH ===
 
* [http://filezilla-project.org/specs/rfc4250.txt RFC 4250] The Secure Shell (SSH) Protocol Assigned Numbers
* [http://filezilla-project.org/specs/rfc4251.txt RFC 4251] The Secure Shell (SSH) Protocol Architecture
* [http://filezilla-project.org/specs/rfc4252.txt RFC 4252] The Secure Shell (SSH) Authentication Protocol
* [http://filezilla-project.org/specs/rfc4253.txt RFC 4253] The Secure Shell (SSH) Transport Layer Protocol
* [http://filezilla-project.org/specs/rfc4254.txt RFC 4254] The Secure Shell (SSH) Connection Protocol
* [http://filezilla-project.org/specs/rfc4255.txt RFC 4255] Using DNS to Securely Publish Secure Shell (SSH) Key Fingerprints
* [http://filezilla-project.org/specs/rfc4256.txt RFC 4256] Generic Message Exchange Authentication for the Secure Shell Protocol (SSH)
* [http://filezilla-project.org/specs/rfc4335.txt RFC 4335] The Secure Shell (SSH) Session Channel Break Extension
* [http://filezilla-project.org/specs/rfc4344.txt RFC 4344] The Secure Shell (SSH) Transport Layer Encryption Modes
* [http://filezilla-project.org/specs/rfc4419.txt RFC 4419] Diffie-Hellman Group Exchange for the Secure Shell (SSH) Transport Layer Protocol
* [http://filezilla-project.org/specs/rfc4462.txt RFC 4462] Generic Security Service Application Program Interface (GSS-API) Authentication and Key Exchange for the Secure Shell (SSH) Protocol
* [http://filezilla-project.org/specs/rfc4716.txt RFC 4716] The Secure Shell (SSH) Public Key File Format
* [http://filezilla-project.org/specs/rfc4819.txt RFC 4819] Secure Shell Public Key Subsystem
 
=== SFTP ===
* [http://filezilla-project.org/specs/draft-ietf-secsh-filexfer-00.txt draft-ietf-secsh-filexfer-00.txt]
* [http://filezilla-project.org/specs/draft-ietf-secsh-filexfer-01.txt draft-ietf-secsh-filexfer-01.txt]
* [http://filezilla-project.org/specs/draft-ietf-secsh-filexfer-02.txt draft-ietf-secsh-filexfer-02.txt] The most commonly used version 3 of the protocol. This is the version implemented in OpenSSH.
* [http://filezilla-project.org/specs/draft-ietf-secsh-filexfer-03.txt draft-ietf-secsh-filexfer-03.txt]
* [http://filezilla-project.org/specs/draft-ietf-secsh-filexfer-04.txt draft-ietf-secsh-filexfer-04.txt]
* [http://filezilla-project.org/specs/draft-ietf-secsh-filexfer-05.txt draft-ietf-secsh-filexfer-05.txt]
* [http://filezilla-project.org/specs/draft-ietf-secsh-filexfer-06.txt draft-ietf-secsh-filexfer-06.txt]
* [http://filezilla-project.org/specs/draft-ietf-secsh-filexfer-07.txt draft-ietf-secsh-filexfer-07.txt]
* [http://filezilla-project.org/specs/draft-ietf-secsh-filexfer-08.txt draft-ietf-secsh-filexfer-08.txt]
* [http://filezilla-project.org/specs/draft-ietf-secsh-filexfer-09.txt draft-ietf-secsh-filexfer-09.txt]
* [http://filezilla-project.org/specs/draft-ietf-secsh-filexfer-10.txt draft-ietf-secsh-filexfer-10.txt]
* [http://filezilla-project.org/specs/draft-ietf-secsh-filexfer-11.txt draft-ietf-secsh-filexfer-11.txt]
* [http://filezilla-project.org/specs/draft-ietf-secsh-filexfer-12.txt draft-ietf-secsh-filexfer-12.txt]
* [http://filezilla-project.org/specs/draft-ietf-secsh-filexfer-13.txt draft-ietf-secsh-filexfer-13.txt]
 
== See also ==
 
* [[File Transfer Protocol|FTP specifications]]
* [[Other specifications]]

Revision as of 18:26, 21 July 2012

, In a universe of aponicatipls, including both latency-sensitive and insensitive aponicatipls, it is difficult to regard the IP suite as truly neutral. TCP/IP is so non-neutral that it was necessary to invent UDP/IP at the same time. And these two transports don't encompass all possible network application paradigms.So no, the TCP/IP protocol stack is not application-neutral in any meaningful sense of the word.You may as well be arguing that the poll tax was not discriminatory because it applied to everyone, rich and poor alike.