Changes between Version 36 and Version 37 of SftpFrontend

Timestamp:

2010-06-18T23:58:55Z (15 years ago)

Author:

davidsarah

Comment:

Server keys with passphrases not supported; be more precise about timestamps; normalization

SftpFrontend

@@ -10 +10 @@
 In practice, that means you can run the Tahoe-LAFS gateway locally on the same machine as your SFTP client (which is a good, efficient, and secure solution), or tunnel your SFTP connection over another secure connection such as ssh tunnel or VPN, or else just accept the risk that someone could snoop on the data that you are sending and receiving over the SFTP connection.
 
+Server keys with passphrases are not supported (#1039).
+
+
 === General compatibility issues ===
 
@@ -20 +23 @@
 See the last section of [source:docs/frontends/FTP-and-SFTP.txt FTP-and-SFTP.txt] for information on how the SFTP frontend treats immutable and mutable files.
 
-The '{{{ctime}}}' and '{{{mtime}}}' fields will not be updated when a mutable file is changed, and do not have exactly the semantics specified by POSIX in other cases.
+The '{{{ctime}}}' and '{{{mtime}}}' fields will always be the same, and are set from the Tahoe {{{linkmotime}}} timestamp, which is changed only when the link from the parent directory is modified (see the 'About the metadata' section of [source:doc/frontends/webapi.txt webapi.txt]). These fields are not updated when a mutable file is changed.
 
 
@@ -55 +58 @@
 === Unicode filenames ===
 
-The SFTP frontend encodes all filenames as UTF-8 when communicating with the client. Support for displaying and copying non-ASCII filenames is likely to vary between clients. If you are using a filesystem that represents names as UTF-8 (including via sshfs), then it should just work, but please report your experience with this. Note that SFTP currently does not perform any [http://en.wikipedia.org/wiki/Unicode_equivalence Unicode normalization] (so for example, filenames copied from a Mac OS X filesystem will remain in NFD); this is likely to change in future.
+The SFTP frontend encodes all filenames as UTF-8 when communicating with the client. Support for displaying and copying non-ASCII filenames is likely to vary between clients. If you are using a filesystem that represents names as UTF-8 (including via sshfs), then it should just work, but please report your experience with this.
 
 Some clients fail to convert filenames to UTF-8; see ticket #1089. In this case they will usually fail to create non-ASCII filenames (although there is a small chance that the name in another encoding will accidentally be decodable as UTF-8), and directory listings will show [http://en.wikipedia.org/wiki/Mojibake mojibake] for non-ASCII names.
+
+As of Tahoe v1.7.0 final, filenames are normalized to NFC, which means that it is not possible to have two files/subdirectories with [http://en.wikipedia.org/wiki/Unicode_equivalence canonically equivalent] names in the same directory. (This does not cause any incompatibility with filesystems that use a different normalization, such as NFD in Mac OS X.)