tahoe-lafs 1.9.2-1 source package in Ubuntu
Changelog
tahoe-lafs (1.9.2-1) unstable; urgency=low [ Bert Agaz ] * New upstream release (Closes: #680083). * Use manpage shipped within upstream release. * Stick to upstream dependency on foolscap >= 0.6.3. -- Micah Anderson <email address hidden> Wed, 04 Jul 2012 17:52:21 +0200
See full publishing history Publishing
Series | Published | Component | Section |
---|
Downloads
File | Size | SHA-256 Checksum |
---|---|---|
tahoe-lafs_1.9.2-1.dsc | 1.9 KiB | 4b2a0f20f92df3e5621a36fb16e473c2740a8e53b2ea089970a533969187c2e1 |
tahoe-lafs_1.9.2.orig.tar.gz | 1.3 MiB | 10b920ddb0da77f94c69e025b15ead33e3fed7a4b756f8bf0eaee3c0278b66b2 |
tahoe-lafs_1.9.2-1.debian.tar.gz | 11.1 KiB | efea9369e169d1dd5f7da62f6d88e465ebb425f0d444fc6a78988a41cbdf1ac9 |
Available diffs
- diff from 1.9.1-1 to 1.9.2-1 (251.6 KiB)
No changes file available.
Binary packages built by this source
- tahoe-lafs: Secure distributed filesystem
Tahoe, the Least Authority File System, is a distributed filesystem that
features high reliability, strong security properties, and a fine-grained
sharing model. Files are encrypted, signed, erasure-coded, then distributed
over multiple servers, such that any (configurable) subset of the servers
will be sufficient to recover the data. The default 3-of-10 configuration
tolerates up to 7 server failures before data becomes unrecoverable.
.
Tahoe offers "provider-independent security": the confidentiality and
integrity of your data do not depend upon the behavior of the servers. The
use of erasure-coding means that reliability and availability depend only
upon a subset of the servers.
.
Tahoe files are accessed through a RESTful web API, a human-oriented web
server interface, and CLI tools.