tahoe-lafs/trac-2024-07-25
2
0
Issues 1.1k Wiki Activity

more on disabling rekeying 

[Imported from Trac: page SftpFrontend, version 59]
davidsarah 2011-01-08 05:34:36 +00:00
parent 807dac944e
commit ed679a56d0
1 changed files with 6 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
SftpFrontend.md

@ -24,7 +24,9 @@ See the last section of [docs/frontends/FTP-and-SFTP.rst](http://tahoe-lafs.org/
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 [bug in support for rekeying <http://twistedmatrix.com/trac/ticket/4395>]a. 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). 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:
* for openssh and sshfs, add the line `RekeyLimit 0` to `~/.ssh/config` (TODO: please test this!)
* for WinSCP, [#WinSCP see that section below].
# Unicode filenames # Unicode filenames
@ -66,6 +68,8 @@ The MacFUSE version of sshfs stores "extended attributes" in files with names st
On Mac OS X, TextEdit and vi are known to have problems editing files on a Tahoe-via-sshfs filesystem. On Mac OS X, TextEdit and vi are known to have problems editing files on a Tahoe-via-sshfs filesystem.
To avoid potential bugs with rekeying, add the line `RekeyLimit 0` to `~/.ssh/config`.
## Gnome virtual filesystem (gvfs) ## Gnome virtual filesystem (gvfs)
@ -84,6 +88,6 @@ In the WinSCP Login dialog, the following options need to be set (some require '
* In the Environment section, set 'UTF-8 encoding for filenames' to 'On'. * 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 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.) * In the Key exchange section under SSH, set both 'Max minutes before rekey' and 'Max data before rekey' to 0.
Note that these options are not persistent unless you save them as a 'Stored session', together with the host name, username, etc. Note that these options are not persistent unless you save them as a 'Stored session', together with the host name, username, etc.