The Tahoe-LAFS decentralized secure filesystem.
Go to file
Sajith Sasidharan ae6e1e9e2f Use io.open() instead of builtin open()
Windows does not like when we open README.rst using builtin open():

  Traceback (most recent call last):
    File "setup.py", line 360, in <module>
      long_description=open('README.rst', 'rU').read(),
    File "c:\hostedtoolcache\windows\python\3.6.8\x64\lib\encodings\cp1252.py", line 23, in decode
      return codecs.charmap_decode(input,self.errors,decoding_table)[0]
  UnicodeDecodeError: 'charmap' codec can't decode byte 0x9d in position 1720: character maps to <undefined>
2021-04-05 19:11:58 -04:00
.circleci Add "docs" job to CircleCI workflow 2021-03-19 15:55:19 -04:00
.github Remove Windows exclusion 2021-04-05 18:34:48 -04:00
docs Merge remote-tracking branch 'origin/master' into 3645.gbs-expanded-motivation 2021-04-03 07:44:58 -04:00
integration Increase timeout, just to be on the safe side. 2021-01-26 12:40:39 -05:00
misc putChild should always be bytes. 2021-02-23 09:18:01 -05:00
newsfragments Add newsfragment 2021-04-05 18:34:33 -04:00
nix Switch back to the full test suite 2021-03-16 15:06:51 -04:00
release-tools refactor more 2018-05-29 13:17:32 -06:00
src/allmydata Rip out all references to the unused IProgress API. 2021-03-31 10:35:25 -04:00
static Remove Nevow from the static script 2020-10-21 10:16:44 -04:00
.coveragerc This is probably a better way to handle multiple Python versions 2020-10-14 13:10:23 -04:00
.gitignore test(vcs): Reconcile devel docs from PR #798 2020-09-30 07:37:52 -07:00
.pre-commit-config.yaml Only run codechecks on changed Python source files 2020-11-19 11:12:08 -05:00
COPYING.GPL Fix repeated 'the' in license text. 2011-08-19 13:48:36 -07:00
COPYING.TGPPL.rst magic first line tells emacs to use utf8+bom 2013-11-08 21:08:05 +00:00
CREDITS credits to Lukas Pirl (buildslaves) 2021-01-09 14:44:10 +01:00
docker-compose.yml add dockerfile for hacking with docker compose file for local environment 2017-09-19 09:25:39 -07:00
Dockerfile Remove $HOME/.cache/ directory after building. 2016-09-26 15:19:04 -07:00
Dockerfile.dev add dockerfile for hacking with docker compose file for local environment 2017-09-19 09:25:39 -07:00
Makefile Update developer docs wrt pre-commit 2020-12-01 09:55:17 -05:00
MANIFEST.in setup.py/MANIFEST.in: include missing files 2017-01-18 16:28:23 -08:00
mypy.ini Incorporate mypy-zope to support zope interfaces. 2020-11-29 13:57:46 -05:00
NEWS.rst update title 2020-03-11 18:41:32 -06:00
pyinstaller.spec Additional hidden imports due to use of Future. 2020-07-03 13:44:47 -04:00
README.rst Add the coveralls.io badge 2021-01-06 17:46:58 -05:00
relnotes.txt bump version to 1.14.0 and update release notes 2020-03-11 17:38:03 -06:00
setup.cfg Add a codecheck for tabs in indentation 2020-08-03 21:14:55 -04:00
setup.py Use io.open() instead of builtin open() 2021-04-05 19:11:58 -04:00
Tahoe.home rename bin/allmydata-tahoe to bin/tahoe. Closes #155. 2007-10-11 03:38:24 -07:00
towncrier.pyproject.toml Give documentation its own towncrier category 2021-04-02 18:19:33 -04:00
tox.ini Use sphinx_rtd_theme when building docs locally 2021-03-09 15:42:48 -05:00
ws_client.py move to different url 2019-03-21 15:00:02 -04:00

Free and Open decentralized data store

image0

Tahoe-LAFS (Tahoe Least-Authority File Store) is the first free software / open-source storage technology that distributes your data across multiple servers. Even if some servers fail or are taken over by an attacker, the entire file store continues to function correctly, preserving your privacy and security.

code of conduct documentation status build status circleci code coverage

Table of contents

💡 About Tahoe-LAFS

Tahoe-LAFS helps you to store files while granting confidentiality, integrity, and availability of your data.

How does it work? You run a client program on your computer, which talks to one or more storage servers on other computers. When you tell your client to store a file, it will encrypt that file, encode it into multiple pieces, then spread those pieces out among various servers. The pieces are all encrypted and protected against modifications. Later, when you ask your client to retrieve the file, it will find the necessary pieces, make sure they havent been corrupted, reassemble them, and decrypt the result.

image2
The image is taken from meejah's blog post at Torproject.org.

The client creates pieces (“shares”) that have a configurable amount of redundancy, so even if some servers fail, you can still get your data back. Corrupt shares are detected and ignored so that the system can tolerate server-side hard-drive errors. All files are encrypted (with a unique key) before uploading, so even a malicious server operator cannot read your data. The only thing you ask of the servers is that they can (usually) provide the shares when you ask for them: you arent relying upon them for confidentiality, integrity, or absolute availability.

Tahoe-LAFS was first designed in 2007, following the "principle of least authority", a security best practice requiring system components to only have the privilege necessary to complete their intended function and not more.

Please read more about Tahoe-LAFS architecture here.

Installation

For more detailed instructions, read docs/INSTALL.rst .

Once tahoe --version works, see docs/running.rst to learn how to set up your first Tahoe-LAFS node.

🤖 Issues

Tahoe-LAFS uses the Trac instance to track issues. Please email jean-paul plus tahoe-lafs at leastauthority dot com for an account.

📑 Documentation

You can find the full Tahoe-LAFS documentation at our documentation site.

💬 Community

Get involved with the Tahoe-LAFS community:

  • Chat with Tahoe-LAFS developers at #tahoe-lafs chat on irc.freenode.net or Slack.
  • Join our weekly conference calls with core developers and interested community members.
  • Subscribe to the tahoe-dev mailing list, the community forum for discussion of Tahoe-LAFS design, implementation, and usage.

🤗 Contributing

As a community-driven open source project, Tahoe-LAFS welcomes contributions of any form:

Before authoring or reviewing a patch, please familiarize yourself with the Coding Standard and the Contributor Code of Conduct.

FAQ

Need more information? Please check our FAQ page.

📄 License

Copyright 2006-2020 The Tahoe-LAFS Software Foundation

You may use this package under the GNU General Public License, version 2 or, at your option, any later version. You may use this package under the Transitive Grace Period Public Licence, version 1.0, or at your choice, any later version. (You may choose to use this package under the terms of either license, at your option.) See the file COPYING.GPL for the terms of the GNU General Public License, version 2. See the file COPYING.TGPPL for the terms of the Transitive Grace Period Public Licence, version 1.0.

See TGPPL.PDF for why the TGPPL exists, graphically illustrated on three slides.