Fedora 20 Update: s3ql-2.9-1.fc20

updates at fedoraproject.org updates at fedoraproject.org
Mon Jul 14 00:53:59 UTC 2014

Fedora Update Notification
2014-07-03 02:49:07

Name        : s3ql
Product     : Fedora 20
Version     : 2.9
Release     : 1.fc20
URL         : https://bitbucket.org/nikratio/s3ql
Summary     : Full-Featured File System for Online Data Storage
Description :
S3QL is a file system that stores all its data online using storage services
like Google Storage, Amazon S3 or OpenStack. S3QL effectively provides a hard
disk of dynamic, infinite capacity that can be accessed from any computer
with Internet access.

S3QL is a standard conforming, full featured UNIX file system that is
conceptually indistinguishable from any local file system. Furthermore, S3QL
has additional features like compression, encryption, data de-duplication,
immutable trees and snapshotting which make it especially suitable for on-line
backup and archival.

S3QL is designed to favor simplicity and elegance over performance and feature-
creep. Care has been taken to make the source code as readable and serviceable
as possible. Solid error detection and error handling have been included
from the very first line, and S3QL comes with extensive automated test cases
for all its components.

== Features ==
* Transparency. Conceptually, S3QL is indistinguishable from a local file
system. For example, it supports hardlinks, symlinks, standard unix
permissions, extended attributes and file sizes up to 2 TB.

* Dynamic Size. The size of an S3QL file system grows and shrinks dynamically
as required.

* Compression. Before storage, all data may compressed with the LZMA, bzip2
or deflate (gzip) algorithm.

* Encryption. After compression (but before upload), all data can AES
encrypted with a 256 bit key. An additional SHA256 HMAC checksum is used to
protect the data against manipulation.

* Data De-duplication. If several files have identical contents, the redundant
data will be stored only once. This works across all files stored in the file
system, and also if only some parts of the files are identical while other
parts differ.
* Immutable Trees. Directory trees can be made immutable, so that their
contents can no longer be changed in any way whatsoever. This can be used to
ensure that backups can not be modified after they have been made.

* Copy-on-Write/Snapshotting. S3QL can replicate entire directory trees
without using any additional storage space. Only if one of the copies is
modified, the part of the data that has been modified will take up additional
storage space. This can be used to create intelligent snapshots that preserve
the state of a directory at different points in time using a minimum amount
of space.

* High Performance independent of network latency. All operations that do not
write or read file contents (like creating directories or moving, renaming,
and changing permissions of files and directories) are very fast because they
are carried out without any network transactions.

S3QL achieves this by saving the entire file and directory structure in a
database. This database is locally cached and the remote copy updated

* Support for low bandwidth connections. S3QL splits file contents into
smaller blocks and caches blocks locally. This minimizes both the number of
network transactions required for reading and writing data, and the amount of
data that has to be transferred when only parts of a file are read or written.

Update Information:

2014-06-28, S3QL 2.9

 * Fix crash when using swift backend and server uses an authentication URL other than /v1.0.

 * Fixed two test failures when running unit tests as root.

 * Fixed problems when receiving an HTTP error without a well-formed XML body from the remote server (this may happen e.g. due to failure in a transparent proxy or load balancer).

 * S3QL now depends on the defusedxml Python module (https://pypi.python.org/pypi/defusedxml/).

 * S3QL is no longer vulnerable to DOS attacks from malicious backend servers. Previously, a malicious server could induce S3QL to consume arbitrary amounts of memory by recursive XML entity expansion.

 * S3QL now supports Google OAuth2 authentication. To use it, specify 'oauth2' as backend login, and a valid OAuth2 refresh token as backend password. To obtain the refresh token, the (new) s3ql_oauth_client command may be used.

 * S3QL now requires version 3.1 or newer of the dugong module.

 * In some cases, transmission errors when reading storage objects from a backend may have been misreported as corrupted backend objects. This has been fixed.

 * S3QL no longer crashes when data corruption occurs in the first few bytes of an LZMA compressed storage object.

 * S3QL now honors the "Retry-After" HTTP header when receiving an XML error from a storage server.

 * Fixed a crash that could occur when the remote server (or some intermediate proxy) sends a non-XML error response.

 * mount.s3ql and fsck.s3ql now use different exit codes to indicate different failure conditions.

* Tue Jul  1 2014 Christopher Meng <rpm at cicku.me> - 2.9-1
- Update to 2.9
* Thu Jun 12 2014 Christopher Meng <rpm at cicku.me> - 2.8.1-1
- Update to 2.8.1
* Tue Sep 24 2013 Marcel Wysocki <maci at satgnu.net> - 2.4-1
- updated to version 2.4, all python3
* Sun Aug  4 2013 Fedora Release Engineering <rel-eng at lists.fedoraproject.org> - 1.13.2-2
- Rebuilt for https://fedoraproject.org/wiki/Fedora_20_Mass_Rebuild

  [ 1 ] Bug #1107269 - s3ql: FTBFS in rawhide
  [ 2 ] Bug #1021215 - s3ql-2.9 is available

This update can be installed with the "yum" update program.  Use
su -c 'yum update s3ql' at the command line.
For more information, refer to "Managing Software with yum",
available at http://docs.fedoraproject.org/yum/.

All packages are signed with the Fedora Project GPG key.  More details on the
GPG keys used by the Fedora Project can be found at

More information about the package-announce mailing list