Changeset 7850359 in trunk

Timestamp:

2014-07-22T05:16:04Z (11 years ago)

Author:

Zooko Wilcox-O'Hearn <zooko@…>

Branches:

master

Children:

bc6304a

Parents:

9947922

Message:

link to Twisted ticket #4633

File:

• docs/frontends/FTP-and-SFTP.rst (modified) (1 diff)

docs/frontends/FTP-and-SFTP.rst ¶

@@ -120 +120 @@
 attacks. The code for encrypting the SFTP connection was not written by the
 Tahoe-LAFS team, and we have not reviewed it as carefully as we have reviewed
-the code for encrypting files and directories in Tahoe-LAFS itself. If you
-can connect to the SFTP server (which is provided by the Tahoe-LAFS gateway)
-only from a client on the same host, then you would be safe from any problem
-with the SFTP connection security. The examples given below enforce this
-policy by including ":interface=127.0.0.1" in the "port" option, which causes
-the server to only accept connections from localhost.
+the code for encrypting files and directories in Tahoe-LAFS itself. (See
+`Twisted ticket #4633`_ for a possible fix to this issue.)
+
+.. _Twisted ticket #4633: https://twistedmatrix.com/trac/ticket/4633
+
+If you can connect to the SFTP server (which is provided by the Tahoe-LAFS
+gateway) only from a client on the same host, then you would be safe from any
+problem with the SFTP connection security. The examples given below enforce
+this policy by including ":interface=127.0.0.1" in the "port" option, which
+causes the server to only accept connections from localhost.
 
 You will use directives in the tahoe.cfg file to tell the SFTP code where to