Twisted 11.0 fixes the rekeying issue
[Imported from Trac: page SftpFrontend, version 66]
parent
8a8705342a
commit
b7acf6f147
|
@ -26,7 +26,7 @@ Deleting a directory via the SFTP frontend will not check that it is empty. The
|
||||||
|
|
||||||
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 ['About the metadata' section of webapi.rst](http://tahoe-lafs.org/trac/tahoe-lafs/browser/docs/frontends/webapi.rst#about-the-metadata)). 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.
|
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 ['About the metadata' section of webapi.rst](http://tahoe-lafs.org/trac/tahoe-lafs/browser/docs/frontends/webapi.rst#about-the-metadata)). 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 by the gateway 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 (for example, 1 GiB to 4 GiB for the openssh client); this problem will typically only affect long-lived connections or very large files. Some clients have options to disable rekeying:
|
Versions of Twisted before 11.0 have [a bug in support for rekeying](http://twistedmatrix.com/trac/ticket/4395). This might cause a hang or 100% CPU usage by the gateway 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 (for example, 1 GiB to 4 GiB for the openssh client); this problem will typically only affect long-lived connections or very large files. Some clients have options to disable rekeying:
|
||||||
* for OpenSSH and sshfs, either use the option `-o [RekeyLimit](RekeyLimit)=0`, or add the line `RekeyLimit=0` to `~/.ssh/config` (TODO: please test this!)
|
* for OpenSSH and sshfs, either use the option `-o [RekeyLimit](RekeyLimit)=0`, or add the line `RekeyLimit=0` to `~/.ssh/config` (TODO: please test this!)
|
||||||
* for WinSCP, [#WinSCP see that section below].
|
* for WinSCP, [#WinSCP see that section below].
|
||||||
|
|
||||||
|
|
Loading…
Reference in a new issue