Package: swift / 2.19.1-1

Metadata

Package Version Patches format
swift 2.19.1-1 3.0 (quilt)

Patch series

view the series file
Patch File delta Description
sphinx_reproducible_build.patch | (download)

api-ref/source/conf.py | 22 14 + 8 - 0 !
doc/source/conf.py | 7 6 + 1 - 0 !
2 files changed, 20 insertions(+), 9 deletions(-)

 use source_date_epoch in docs to make build reproducible
syslog_log_name.patch | (download)

etc/account-server.conf-sample | 10 5 + 5 - 0 !
etc/container-reconciler.conf-sample | 2 1 + 1 - 0 !
etc/container-server.conf-sample | 12 6 + 6 - 0 !
etc/drive-audit.conf-sample | 2 1 + 1 - 0 !
etc/internal-client.conf-sample | 2 1 + 1 - 0 !
etc/object-expirer.conf-sample | 2 1 + 1 - 0 !
etc/object-server.conf-sample | 12 6 + 6 - 0 !
etc/proxy-server.conf-sample | 22 11 + 11 - 0 !
swift/container/sync.py | 2 1 + 1 - 0 !
9 files changed, 33 insertions(+), 33 deletions(-)

 set log_name for swift services in default configs
fix decryption of object if metadata is missing.patch | (download)

swift/common/middleware/crypto/decrypter.py | 11 11 + 0 - 0 !
swift/common/middleware/crypto/keymaster.py | 10 8 + 2 - 0 !
2 files changed, 19 insertions(+), 2 deletions(-)

 fix decryption of objects if metadata is missing
 In some cases, the Meta-Crypto is missing from object store's
 metadata. If this happens, then Swift is enable to decrypt objects,
 as it uses the object name instead of the "path" field that has been
 used for encryption, resulting in a completely wrong decryption.
 .
 This patch fixes the problem by using the right "path" field as one of
 the elements used to decrypt.