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

openssh/sshfs options 

[Imported from Trac: page SftpFrontend, version 60]
davidsarah 2011-01-08 05:41:18 +00:00
parent ed679a56d0
commit 0528618aee
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
SftpFrontend.md

@ -25,7 +25,7 @@ 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 [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 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 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].