1 | ANNOUNCING Tahoe, the Least-Authority File Store, v1.18.0 |
---|
2 | |
---|
3 | The Tahoe-LAFS team is pleased to announce version 1.18.0 of |
---|
4 | Tahoe-LAFS, an extremely reliable decentralized storage |
---|
5 | system. Get it with "pip install tahoe-lafs", or download a |
---|
6 | tarball here: |
---|
7 | |
---|
8 | https://tahoe-lafs.org/downloads |
---|
9 | |
---|
10 | Tahoe-LAFS is the first distributed storage system to offer |
---|
11 | "provider-independent security" — meaning that not even the |
---|
12 | operators of your storage servers can read or alter your data |
---|
13 | without your consent. Here is the one-page explanation of its |
---|
14 | unique security and fault-tolerance properties: |
---|
15 | |
---|
16 | https://tahoe-lafs.readthedocs.org/en/latest/about.html |
---|
17 | |
---|
18 | The previous stable release of Tahoe-LAFS was v1.17.1, released on |
---|
19 | January 7, 2022. |
---|
20 | |
---|
21 | This release drops support for Python 2 and for Python 3.6 and earlier. |
---|
22 | twistd.pid is no longer used (in favour of one with pid + process creation time). |
---|
23 | A collection of minor bugs and issues were also fixed. |
---|
24 | |
---|
25 | Please see ``NEWS.rst`` [1] for a complete list of changes. |
---|
26 | |
---|
27 | |
---|
28 | WHAT IS IT GOOD FOR? |
---|
29 | |
---|
30 | With Tahoe-LAFS, you distribute your data across multiple |
---|
31 | servers. Even if some of the servers fail or are taken over |
---|
32 | by an attacker, the entire file store continues to function |
---|
33 | correctly, preserving your privacy and security. You can |
---|
34 | easily share specific files and directories with other people. |
---|
35 | |
---|
36 | In addition to the core storage system itself, volunteers |
---|
37 | have built other projects on top of Tahoe-LAFS and have |
---|
38 | integrated Tahoe-LAFS with existing systems, including |
---|
39 | Windows, JavaScript, iPhone, Android, Hadoop, Flume, Django, |
---|
40 | Puppet, bzr, mercurial, perforce, duplicity, TiddlyWiki, and |
---|
41 | more. See the Related Projects page on the wiki [3]. |
---|
42 | |
---|
43 | We believe that strong cryptography, Free and Open Source |
---|
44 | Software, erasure coding, and principled engineering practices |
---|
45 | make Tahoe-LAFS safer than RAID, removable drive, tape, |
---|
46 | on-line backup or cloud storage. |
---|
47 | |
---|
48 | This software is developed under test-driven development, and |
---|
49 | there are no known bugs or security flaws which would |
---|
50 | compromise confidentiality or data integrity under recommended |
---|
51 | use. (For all important issues that we are currently aware of |
---|
52 | please see the known_issues.rst file [2].) |
---|
53 | |
---|
54 | |
---|
55 | COMPATIBILITY |
---|
56 | |
---|
57 | This release should be compatible with the version 1 series of |
---|
58 | Tahoe-LAFS. Clients from this release can write files and |
---|
59 | directories in the format used by clients of all versions back |
---|
60 | to v1.0 (which was released March 25, 2008). Clients from this |
---|
61 | release can read files and directories produced by clients of |
---|
62 | all versions since v1.0. |
---|
63 | |
---|
64 | Network connections are limited by the Introducer protocol in use. If |
---|
65 | the Introducer is running v1.10 or v1.11, then servers from this |
---|
66 | release can serve clients of all versions back to v1.0 . If it is |
---|
67 | running v1.12 or higher, then they can only serve clients back to |
---|
68 | v1.10. Clients from this release can use servers back to v1.10, but |
---|
69 | not older servers. |
---|
70 | |
---|
71 | Except for the new optional MDMF format, we have not made any |
---|
72 | intentional compatibility changes. However we do not yet have |
---|
73 | the test infrastructure to continuously verify that all new |
---|
74 | versions are interoperable with previous versions. We intend |
---|
75 | to build such an infrastructure in the future. |
---|
76 | |
---|
77 | This is the twenty-second release in the version 1 series. This |
---|
78 | series of Tahoe-LAFS will be actively supported and maintained |
---|
79 | for the foreseeable future, and future versions of Tahoe-LAFS |
---|
80 | will retain the ability to read and write files compatible |
---|
81 | with this series. |
---|
82 | |
---|
83 | |
---|
84 | LICENCE |
---|
85 | |
---|
86 | You may use this package under the GNU General Public License, |
---|
87 | version 2 or, at your option, any later version. See the file |
---|
88 | "COPYING.GPL" [4] for the terms of the GNU General Public |
---|
89 | License, version 2. |
---|
90 | |
---|
91 | You may use this package under the Transitive Grace Period |
---|
92 | Public Licence, version 1 or, at your option, any later |
---|
93 | version. (The Transitive Grace Period Public Licence has |
---|
94 | requirements similar to the GPL except that it allows you to |
---|
95 | delay for up to twelve months after you redistribute a derived |
---|
96 | work before releasing the source code of your derived work.) |
---|
97 | See the file "COPYING.TGPPL.rst" [5] for the terms of the |
---|
98 | Transitive Grace Period Public Licence, version 1. |
---|
99 | |
---|
100 | (You may choose to use this package under the terms of either |
---|
101 | licence, at your option.) |
---|
102 | |
---|
103 | |
---|
104 | INSTALLATION |
---|
105 | |
---|
106 | Tahoe-LAFS works on Linux, Mac OS X, Windows, Solaris, *BSD, |
---|
107 | and probably most other systems. Start with "docs/INSTALL.rst" |
---|
108 | [6]. |
---|
109 | |
---|
110 | |
---|
111 | HACKING AND COMMUNITY |
---|
112 | |
---|
113 | Please join us on the mailing list [7]. Patches are gratefully |
---|
114 | accepted -- the Roadmap page [8] shows the next improvements |
---|
115 | that we plan to make and CREDITS [9] lists the names of people |
---|
116 | who've contributed to the project. The Dev page [10] contains |
---|
117 | resources for hackers. |
---|
118 | |
---|
119 | |
---|
120 | SPONSORSHIP |
---|
121 | |
---|
122 | A special thanks goes out to Least Authority Enterprises [12], |
---|
123 | which employs several Tahoe-LAFS developers, for their |
---|
124 | continued support. |
---|
125 | |
---|
126 | HACK TAHOE-LAFS! |
---|
127 | |
---|
128 | If you can find a security flaw in Tahoe-LAFS which is serious |
---|
129 | enough that we feel compelled to warn our users and issue a fix, |
---|
130 | then we will award you with a customized t-shirt with your |
---|
131 | exploit printed on it and add you to the "Hack Tahoe-LAFS Hall |
---|
132 | Of Fame" [13]. |
---|
133 | |
---|
134 | |
---|
135 | ACKNOWLEDGEMENTS |
---|
136 | |
---|
137 | This is the twentieth release of Tahoe-LAFS to be created solely as a |
---|
138 | labor of love by volunteers. Thank you very much to the team of |
---|
139 | "hackers in the public interest" who make Tahoe-LAFS possible. |
---|
140 | |
---|
141 | meejah |
---|
142 | on behalf of the Tahoe-LAFS team |
---|
143 | |
---|
144 | October 1, 2022 |
---|
145 | Planet Earth |
---|
146 | |
---|
147 | |
---|
148 | [1] https://github.com/tahoe-lafs/tahoe-lafs/blob/tahoe-lafs-1.18.0/NEWS.rst |
---|
149 | [2] https://github.com/tahoe-lafs/tahoe-lafs/blob/master/docs/known_issues.rst |
---|
150 | [3] https://tahoe-lafs.org/trac/tahoe-lafs/wiki/RelatedProjects |
---|
151 | [4] https://github.com/tahoe-lafs/tahoe-lafs/blob/tahoe-lafs-1.18.0/COPYING.GPL |
---|
152 | [5] https://github.com/tahoe-lafs/tahoe-lafs/blob/tahoe-lafs-1.18.0/COPYING.TGPPL.rst |
---|
153 | [6] https://tahoe-lafs.readthedocs.org/en/tahoe-lafs-1.18.0/INSTALL.html |
---|
154 | [7] https://lists.tahoe-lafs.org/mailman/listinfo/tahoe-dev |
---|
155 | [8] https://tahoe-lafs.org/trac/tahoe-lafs/roadmap |
---|
156 | [9] https://github.com/tahoe-lafs/tahoe-lafs/blob/master/CREDITS |
---|
157 | [10] https://tahoe-lafs.org/trac/tahoe-lafs/wiki/Dev |
---|
158 | [12] https://leastauthority.com/ |
---|
159 | [13] https://tahoe-lafs.org/hacktahoelafs/ |
---|
160 | [14] https://github.com/warner/magic-wormhole |
---|