warn users not to rely on PyCrypto #1192

New Issue

zooko · 2010-09-03T13:24:25Z

zooko commented

2010-09-03 13:24:25 +00:00

The PyCrypto AES implementation has no defenses against timing attacks, and also it seems like nobody has examined PyCrypto carefully for safety. (Although I audited the PyCrypto RNG and it was a mess but I didn't find any real holes.) People shouldn't rely on PyCrypto for their confidentiality. The way this affects Tahoe-LAFS is that people should run the Tahoe-LAFS gateway, which contains an SFTP server, locally to where they are running their SFTP client. Add a note to this effect to the appropriate documentation, presumably source:docs/frontends/FTP-and-SFTP.txt.

zooko added the

labels 2010-09-03 13:24:25 +00:00

zooko added this to the 1.8.0 milestone 2010-09-03 13:24:25 +00:00

francois commented

2010-09-04 13:37:45 +00:00

I propose to add the following text as a second paragraph in Configuring SFTP Access of source:docs/frontends/FTP-and-SFTP.txt.

Beware that the SFTP server should only run locally because PyCrypto
cannot currently be relied on for confidentiality purpose. The PyCrypto
AES implementation has no defenses against timing attacks, and also it
seems like nobody has examined PyCrypto carefully for safety.

I propose to add the following text as a second paragraph in **Configuring SFTP Access** of source:docs/frontends/FTP-and-SFTP.txt. ``` Beware that the SFTP server should only run locally because PyCrypto cannot currently be relied on for confidentiality purpose. The PyCrypto AES implementation has no defenses against timing attacks, and also it seems like nobody has examined PyCrypto carefully for safety. ```

francois commented

2010-09-04 13:55:49 +00:00

Attachment doc-patch-1192.dpatch (5476 bytes) added

**Attachment** doc-patch-1192.dpatch (5476 bytes) added

doc-patch-1192.dpatch

5.3 KiB

francois commented

2010-09-04 13:58:26 +00:00

This patch doc-patch-1192.dpatch contains another, more detailed, explanation written by Zooko.

This patch [doc-patch-1192.dpatch](/tahoe-lafs/trac-2024-07-25/attachments/000078ac-0aec-17ce-3bff-960d3a2ecb63) contains another, more detailed, explanation written by Zooko.

davidsarah commented

2010-09-10 19:27:14 +00:00

If you can run the SFTP server (which is provided by the Tahoe-LAFS gateway) on the same host as your SFTP client then you would be safe from any problem with the SFTP connection security.

This depends on the server binding only to localhost. Change it to something like:

The SFTP server is provided by the Tahoe-LAFS gateway. If you can run it on the same host as your SFTP client, and configured to accept connections only from localhost (using ":interface=127.0.0.1" in the port option as in the examples below), then you would be safe from any problem with the SFTP connection security.

> If you can run the SFTP server (which is provided by the Tahoe-LAFS gateway) on the same host as your SFTP client then you would be safe from any problem with the SFTP connection security. This depends on the server binding only to localhost. Change it to something like: > The SFTP server is provided by the Tahoe-LAFS gateway. If you can run it on the same host as your SFTP client, and configured to accept connections only from localhost (using ":interface=127.0.0.1" in the port option as in the examples below), then you would be safe from any problem with the SFTP connection security.

david-sarah@jacaranda.org commented

2010-09-10 20:14:01 +00:00

In changeset:7d8e17c4434c5c86:

docs/frontends/FTP-and-SFTP.txt: warn users about connecting to the FTP and SFTP servers remotely. Fixes #1192

In changeset:7d8e17c4434c5c86: ``` docs/frontends/FTP-and-SFTP.txt: warn users about connecting to the FTP and SFTP servers remotely. Fixes #1192 ```

tahoe-lafs added the

fixed

label 2010-09-10 20:14:01 +00:00

tahoe-lafs closed this issue

2010-09-10 20:14:01 +00:00

Sign in to join this conversation.

No Label

LeastAuthority.com automation

code-frontend-ftp-sftp

code-frontend-magic-folder

somebody else's problem

No Milestone

No Assignees

2 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Reference: tahoe-lafs/trac-2024-07-25#1192