Changes between Version 57 and Version 58 of SftpFrontend

Timestamp:

2011-01-08T05:19:46Z (13 years ago)

Author:

davidsarah

Comment:

twisted rekeying bug

SftpFrontend

@@ -24 +24 @@
 
 The '{{{ctime}}}' and '{{{mtime}}}' attributes 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 [http://tahoe-lafs.org/trac/tahoe-lafs/browser/docs/frontends/webapi.rst#about-the-metadata 'About the metadata' section of webapi.rst]). These fields are not updated when the contents of a mutable file are changed. The SFTP protocol and the server are able to represent dates up to the year 2106, but some clients may print dates incorrectly after 2037.
+
+Versions of Twisted up to and including 10.2 have [a bug in support for rekeying http://twistedmatrix.com/trac/ticket/4395]. This might cause a hang or 100% CPU usage when a client tries to rekey. Depending on the client, rekeying may be triggered based on a time interval or the amount of data sent; this problem will typically only affect long-lived connections or very large files. Some clients have options to disable rekeying (see below for openssh, sshfs and WinSCP).
 
 
@@ -83 +85 @@
  * In the Environment section, set 'UTF-8 encoding for filenames' to 'On'.
  * In the Connection section, set 'Server response timeout' to the maximum 6000 seconds.
+ * In the Key exchange section under SSH, set both 'Max minutes before rekey' and 'Max data before rekey' to 0. (This works around a potential bug in Twisted's SSH implementation by disabling rekeying.)
 
 Note that these options are not persistent unless you save them as a 'Stored session', together with the host name, username, etc.