|
|
| Line 1: |
Line 1: |
| The ''SSH File Transfer Protocol'' (SFTP) is used to transfer files over a cryptographically protected ''Secure Shell'' (SSH) connection.
| | I went looking how my dioibiruttsn handles this (since it apparently doesn't use the mime.types provided by Apache, but has its own package), and found the following email message:On Fri Aug 31 10:51:55 2007, someone wrote:> I have noticed that there doesn't seem to be any way to extract all> the current mimetypes and their extensions from the iana website.> This is particularly difficult for Linux distros in particular when> they want to update their mime.types file because they have to> manually sift through the iana website to see what has changed. If> you provided a file that dynamically displayed all mime types and> their file extensions from your database, it would smooth over the> update process for many people. If you currently already have such a> file, could you send me the link to it?I'm afraid we don't provide such a file. We are, however, currentlyworking on making the IANA-maintained registries available in XMLformat.Best regards,Amanda BaberIANA |
| | |
| == 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]]
| |
I went looking how my dioibiruttsn handles this (since it apparently doesn't use the mime.types provided by Apache, but has its own package), and found the following email message:On Fri Aug 31 10:51:55 2007, someone wrote:> I have noticed that there doesn't seem to be any way to extract all> the current mimetypes and their extensions from the iana website.> This is particularly difficult for Linux distros in particular when> they want to update their mime.types file because they have to> manually sift through the iana website to see what has changed. If> you provided a file that dynamically displayed all mime types and> their file extensions from your database, it would smooth over the> update process for many people. If you currently already have such a> file, could you send me the link to it?I'm afraid we don't provide such a file. We are, however, currentlyworking on making the IANA-maintained registries available in XMLformat.Best regards,Amanda BaberIANA
