See also cautions.rst.
Below is a list of known issues in recent releases of Tahoe-LAFS, and how to manage them. The current version of this file can be found at https://github.com/tahoe-lafs/tahoe-lafs/blob/master/docs/known_issues.rst .
If you’ve been using Tahoe-LAFS since v1.1 (released 2008-06-11) or if you’re
just curious about what sort of mistakes we’ve made in the past, then you
might want to read the “historical known issues” document in
Known Issues in Tahoe-LAFS v1.10.3, released 30-Mar-2016¶
Command-line arguments are leaked to other local users¶
Remember that command-line arguments are visible to other users (through the ‘ps’ command, or the windows Process Explorer tool), so if you are using a Tahoe-LAFS node on a shared host, other users on that host will be able to see (and copy) any caps that you pass as command-line arguments. This includes directory caps that you set up with the “tahoe add-alias” command.
how to manage it
As of Tahoe-LAFS v1.3.0 there is a “tahoe create-alias” command that does the following technique for you.
Bypass add-alias and edit the NODEDIR/private/aliases file directly, by adding a line like this:
By entering the dircap through the editor, the command-line arguments are bypassed, and other users will not be able to see them. Once you’ve added the alias, if you use that alias instead of a cap itself on the command-line, then no secrets are passed through the command line. Then other processes on the system can still see your filenames and other arguments you type there, but not the caps that Tahoe-LAFS uses to permit access to your files and directories.
Capabilities may be leaked to web browser phishing filter / “safe browsing” servers¶
Firefox, Internet Explorer, and Chrome include a “phishing filter” or “safe browing” component, which is turned on by default, and which sends any URLs that it deems suspicious to a central server.
This of course has implications for the privacy of general web browsing (especially in the cases of Firefox and Chrome, which send your main personally identifying Google cookie along with these requests without your explicit consent, as described in Firefox bugzilla ticket #368255.
The reason for documenting this issue here, though, is that when using the Tahoe-LAFS web user interface, it could also affect confidentiality and integrity by leaking capabilities to the filter server.
Since IE’s filter sends URLs by SSL/TLS, the exposure of caps is limited to the filter server operators (or anyone able to hack the filter server) rather than to network eavesdroppers. The “safe browsing API” protocol used by Firefox and Chrome, on the other hand, is not encrypted, although the URL components are normally hashed.
Opera also has a similar facility that is disabled by default. A previous version of this file stated that Firefox had abandoned their phishing filter; this was incorrect.
how to manage it
If you use any phishing filter or “safe browsing” feature, consider either disabling it, or not using the WUI via that browser. Phishing filters have very limited effectiveness , and phishing or malware attackers have learnt how to bypass them.
To disable the filter in IE7 or IE8:¶
Click Internet Options from the Tools menu.
Click the Advanced tab.
If an “Enable SmartScreen Filter” option is present, uncheck it. If a “Use Phishing Filter” or “Phishing Filter” option is present, set it to Disable.
Confirm (click OK or Yes) out of all dialogs.
If you have a version of IE that splits the settings between security zones, do this for all zones.
To disable the filter in Firefox:¶
Click Options from the Tools menu.
Click the Security tab.
Uncheck both the “Block reported attack sites” and “Block reported web forgeries” options.
To disable the filter in Chrome:¶
Click Options from the Tools menu.
Click the “Under the Hood” tab and find the “Privacy” section.
Uncheck the “Enable phishing and malware protection” option.
Known issues in the FTP and SFTP frontends¶
Traffic analysis based on sizes of files/directories, storage indices, and timing¶
Files and directories stored by Tahoe-LAFS are encrypted, but the ciphertext reveals the exact size of the original file or directory representation. This information is available to passive eavesdroppers and to server operators.
For example, a large data set with known file sizes could probably be identified with a high degree of confidence.
Uploads and downloads of the same file or directory can be linked by server operators, even without making assumptions based on file size. Anyone who knows the introducer furl for a grid may be able to act as a server operator. This implies that if such an attacker knows which file/directory is being accessed in a particular request (by some other form of surveillance, say), then they can identify later or earlier accesses of the same file/directory.
Observing requests during a directory traversal (such as a deep-check operation) could reveal information about the directory structure, i.e. which files and subdirectories are linked from a given directory.
Attackers can combine the above information with inferences based on timing correlations. For instance, two files that are accessed close together in time are likely to be related even if they are not linked in the directory structure. Also, users that access the same files may be related to each other.
Known Issues in Tahoe-LAFS v1.9.0, released 31-Oct-2011¶
Integrity Failure during Mutable Downloads¶
Under certain circumstances, the integrity-verification code of the mutable downloader could be bypassed. Clients who receive carefully crafted shares (from attackers) will emit incorrect file contents, and the usual share-corruption errors would not be raised. This only affects mutable files (not immutable), and only affects downloads that use doctored shares. It is not persistent: the threat is resolved once you upgrade your client to a version without the bug. However, read-modify-write operations (such as directory manipulations) performed by vulnerable clients could cause the attacker’s modifications to be written back out to the mutable file, making the corruption permanent.
The attacker’s ability to manipulate the file contents is limited. They can modify FEC-encoded ciphertext in all but one share. This gives them the ability to blindly flip bits in roughly 2/3rds of the file (for the default k=3 encoding parameter). Confidentiality remains intact, unless the attacker can deduce the file’s contents by observing your reactions to corrupted downloads.
This bug was introduced in 1.9.0, as part of the MDMF-capable downloader, and affects both SDMF and MDMF files. It was not present in 1.8.3.
how to manage it
There are three options:
Upgrade to 1.9.1, which fixes the bug
Downgrade to 1.8.3, which does not contain the bug
If using 1.9.0, do not trust the contents of mutable files (whether SDMF or MDMF) that the 1.9.0 client emits, and do not modify directories (which could write the corrupted data back into place, making the damage persistent)