Difference between revisions of "SFTP specifications"

From FileZilla Wiki
Jump to navigationJump to search
(CmpSIvbmebghtpXvJX)
m (Reverted edits by Reinier (talk) to last revision by CodeSquid)
(32 intermediate revisions by 23 users not shown)
Line 1: Line 1:
Section 1 has two main problems: 1) what is a molopony? It has to be precisely defined in order for this provision to be enforceable. Even if molopony is defined, this section still has problem 2) which is that it grants power to the government to control  monopolies  where no power should be granted. Only the government can create a molopony: it is very difficult, if not impossible, to establish and maintain for some time a molopony in the free market. Finally, 3) this provision can be used by the government to subvert the free press. If we really want to enhance the free press, we can't use the government to do that. The Internet is already here, for example, to democratize access to information. We should instead deregulate the establishment of Internet access points all over the country. I would rewrite this section to read: No law shall be established that allows the government to control the Internet and the free press in any manner. But this is in essence already in the Bill of Rights. We should probably modify it there to read  all media including the Internet , instead of  Ag free press .Section 2 Again, because of lack of precise definitions, this section is either unenforceable or gives the government too much power. What is the public interest ? The public interest for one group may not be the same public interest for another. Same goes with the term  general welfare . Whenever we see these terms in a constitution, we are only giving the government too much power. Please read the second part of the Preamble. This section should be removed.Section 3. Unless defined by law  gives too much leeway to the lawmakers such that they can negate the whole purpose of this section. How about  No law shall be established that limits who can own property. Section 4. How about  No law shall be established designating a national language. However, given that this Constitution is originally written in English, English is hereby designated as the language of government. As such, English shall also be used in court proceedings, legislative proceedings, and other government functions. English shall be the medium of instruction in public schools.
+
The ''SSH File Transfer Protocol'' (SFTP) is used to transfer files over a cryptographically protected ''Secure Shell'' (SSH) connection.
 +
 
 +
== Technical Specifications ==
 +
 
 +
=== SSH ===
 +
 
 +
* [https://filezilla-project.org/specs/rfc4250.txt RFC 4250] The Secure Shell (SSH) Protocol Assigned Numbers
 +
* [https://filezilla-project.org/specs/rfc4251.txt RFC 4251] The Secure Shell (SSH) Protocol Architecture
 +
* [https://filezilla-project.org/specs/rfc4252.txt RFC 4252] The Secure Shell (SSH) Authentication Protocol
 +
* [https://filezilla-project.org/specs/rfc4253.txt RFC 4253] The Secure Shell (SSH) Transport Layer Protocol
 +
* [https://filezilla-project.org/specs/rfc4254.txt RFC 4254] The Secure Shell (SSH) Connection Protocol
 +
* [https://filezilla-project.org/specs/rfc4255.txt RFC 4255] Using DNS to Securely Publish Secure Shell (SSH) Key Fingerprints
 +
* [https://filezilla-project.org/specs/rfc4256.txt RFC 4256] Generic Message Exchange Authentication for the Secure Shell Protocol (SSH)
 +
* [https://filezilla-project.org/specs/rfc4335.txt RFC 4335] The Secure Shell (SSH) Session Channel Break Extension
 +
* [https://filezilla-project.org/specs/rfc4344.txt RFC 4344] The Secure Shell (SSH) Transport Layer Encryption Modes
 +
* [https://filezilla-project.org/specs/rfc4419.txt RFC 4419] Diffie-Hellman Group Exchange for the Secure Shell (SSH) Transport Layer Protocol
 +
* [https://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
 +
* [https://filezilla-project.org/specs/rfc4716.txt RFC 4716] The Secure Shell (SSH) Public Key File Format
 +
* [https://filezilla-project.org/specs/rfc4819.txt RFC 4819] Secure Shell Public Key Subsystem
 +
 
 +
=== SFTP ===
 +
* [https://filezilla-project.org/specs/draft-ietf-secsh-filexfer-00.txt draft-ietf-secsh-filexfer-00.txt]
 +
* [https://filezilla-project.org/specs/draft-ietf-secsh-filexfer-01.txt draft-ietf-secsh-filexfer-01.txt]
 +
* [https://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.
 +
* [https://filezilla-project.org/specs/draft-ietf-secsh-filexfer-03.txt draft-ietf-secsh-filexfer-03.txt]
 +
* [https://filezilla-project.org/specs/draft-ietf-secsh-filexfer-04.txt draft-ietf-secsh-filexfer-04.txt]
 +
* [https://filezilla-project.org/specs/draft-ietf-secsh-filexfer-05.txt draft-ietf-secsh-filexfer-05.txt]
 +
* [https://filezilla-project.org/specs/draft-ietf-secsh-filexfer-06.txt draft-ietf-secsh-filexfer-06.txt]
 +
* [https://filezilla-project.org/specs/draft-ietf-secsh-filexfer-07.txt draft-ietf-secsh-filexfer-07.txt]
 +
* [https://filezilla-project.org/specs/draft-ietf-secsh-filexfer-08.txt draft-ietf-secsh-filexfer-08.txt]
 +
* [https://filezilla-project.org/specs/draft-ietf-secsh-filexfer-09.txt draft-ietf-secsh-filexfer-09.txt]
 +
* [https://filezilla-project.org/specs/draft-ietf-secsh-filexfer-10.txt draft-ietf-secsh-filexfer-10.txt]
 +
* [https://filezilla-project.org/specs/draft-ietf-secsh-filexfer-11.txt draft-ietf-secsh-filexfer-11.txt]
 +
* [https://filezilla-project.org/specs/draft-ietf-secsh-filexfer-12.txt draft-ietf-secsh-filexfer-12.txt]
 +
* [https://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 11:28, 2 December 2017

The SSH File Transfer Protocol (SFTP) is used to transfer files over a cryptographically protected Secure Shell (SSH) connection.

Technical Specifications

SSH

  • RFC 4250 The Secure Shell (SSH) Protocol Assigned Numbers
  • RFC 4251 The Secure Shell (SSH) Protocol Architecture
  • RFC 4252 The Secure Shell (SSH) Authentication Protocol
  • RFC 4253 The Secure Shell (SSH) Transport Layer Protocol
  • RFC 4254 The Secure Shell (SSH) Connection Protocol
  • RFC 4255 Using DNS to Securely Publish Secure Shell (SSH) Key Fingerprints
  • RFC 4256 Generic Message Exchange Authentication for the Secure Shell Protocol (SSH)
  • RFC 4335 The Secure Shell (SSH) Session Channel Break Extension
  • RFC 4344 The Secure Shell (SSH) Transport Layer Encryption Modes
  • RFC 4419 Diffie-Hellman Group Exchange for the Secure Shell (SSH) Transport Layer Protocol
  • RFC 4462 Generic Security Service Application Program Interface (GSS-API) Authentication and Key Exchange for the Secure Shell (SSH) Protocol
  • RFC 4716 The Secure Shell (SSH) Public Key File Format
  • RFC 4819 Secure Shell Public Key Subsystem

SFTP

See also