From 12faebfdd50ada6e096c14f11c1dfd7f771ca2da Mon Sep 17 00:00:00 2001
From: daira <>
Date: Sun, 5 Feb 2017 12:04:35 +0000
Subject: [PATCH] Pycrypto is no longer used with recent Twisted

[Imported from Trac: page SftpFrontend, version 92]
---
 SftpFrontend.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/SftpFrontend.md b/SftpFrontend.md
index 46fdc4b..9768216 100644
--- a/SftpFrontend.md
+++ b/SftpFrontend.md
@@ -5,6 +5,8 @@ See [docs/frontends/FTP-and-SFTP.rst (.txt in releases before v1.8.1)](http://ta
 
 # Security
 
+(Note: the following issue no longer applies with recent versions of Tahoe and Twisted; need version details.)
+
 The security of the connection between the SFTP client and gateway is dependent on the PyCrypto library, which has not been reviewed to the same extent as the pycryptopp library that we use elsewhere in Tahoe-LAFS. In particular, the AES implementation in PyCrypto might be vulnerable to timing attacks and the RSA implementation in PyCrypto up to and including at least PyCrypto v2.4.1 is vulnerable to timing attacks. Either of these could potentially, depending on the situation, allow a remote attacker to break the encryption protecting the SFTP connection between your SFTP client and the Tahoe-LAFS gateway process that is acting as SFTP server. Therefore we do not recommend that you rely on the confidentiality or authentication provided by this SSH connection in the current release.
 
 In practice, that means you can run the Tahoe-LAFS gateway locally on the same machine as your SFTP client (which is a good, efficient, and secure solution), or tunnel your SFTP connection over another secure connection such as ssh tunnel or VPN, or else just accept the risk that someone could snoop on the data that you are sending and receiving over the SFTP connection.