Debian Patches
Status for swift/2.26.0-10+deb11u1
| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| CVE-2022-47950-stable-victoria.patch | CVE-2022-47950: s3api: Prevent XXE injections Previously, clients could use XML external entities (XXEs) to read arbitrary files from proxy-servers and inject the content into the request. Since many S3 APIs reflect request content back to the user, this could be used to extract any secrets that the swift user could read, such as tempauth credentials, keymaster secrets, etc. . Now, disable entity resolution -- any unknown entities will be replaced with an empty string. Without resolving the entities, the request is still processed. =================================================================== |
Aymeric Ducroquetz <aymeric.ducroquetz@ovhcloud.com> | no | debian upstream | upstream, https://review.opendev.org/c/openstack/swift/+/870828 | 2022-01-19 |
| disable_sphinxcontrib_rsvgconverter.patch | Disable sphinxcontrib.rsvgconverter extension =================================================================== |
Ondej Nov <novy@ondrej.org> | not-needed | 2020-02-12 | ||
| fix-eventlet-monkey-patching-with-py3.7.patch | Fix eventlet monkey patching with Python >= 3.7 This is inspired from: https://github.com/openstack/nova/commit/2078ef850c93b47ec1bcd044450b589d7a8fc0b5 Let's see if this fixes it... =================================================================== |
Thomas Goirand <zigo@debian.org> | no | 2020-10-29 | ||
| Fix__exit__calls.patch | Fix __exit__ calls The context manager protocol requires that __exit__ be called with three args: type, value, and traceback. In some places, we didn't include any args at all, leading to test failures during clean-up. =================================================================== |
Tim Burke <tim.burke@gmail.com> | no | upstream, https://review.opendev.org/c/openstack/swift/+/770666 | 2021-01-13 | |
| Get_unit_tests_passing_on_py39.patch | [PATCH] Get unit tests passing on py39 They finally got rid of Thread.isAlive, having added Thread.is_alive as an alias back in 2.6. . array.tostring is also gone, though I'm not sure why we didn't use tofile to begin with. diff --git a/swift/common/ring/ring.py b/swift/common/ring/ring.py index ce31fc499..0d3244036 100644 |
Tim Burke <tim.burke@gmail.com> | no | https://review.opendev.org/758631 | 2020-10-18 | |
| set-default-workers-value.patch | Set default workers value Since the package switched to uwsgi and now reads this value, it can't be left as "auto" an commented out. |
Thomas Goirand <zigo@debian.org> | not-needed | 2020-10-30 | ||
| syslog_log_name.patch | Set log_name for Swift services in default configs =================================================================== |
Ondej Nov <novy@ondrej.org> | not-needed | 2016-07-05 | ||
| Turn_off_logging.logThreads_when_monkey-patched.patch | Turn off logging.logThreads when monkey-patched We've seen proxy-servers lock up while trying to log client disconnects. The trouble is that we happen to do this while we're *already* trying to log *something else*. If the timing works out particularly badly, we end up with a double-call to (an eventlet-patched) threading.current_thread(), which needs to enumerate all pthreads, which uses a non-re-entrant lock in CPython. . The most expedient solution seems to be disabling logThreads so we never call threading.current_thread(). diff --git a/swift/common/utils.py b/swift/common/utils.py index 83417ff..b31e9af 100644 |
Tim Burke <tim.burke@gmail.com> | no | https://review.opendev.org/c/openstack/swift/+/752593 | 2021-03-24 |
Showing 1 to 8 of 8 entries
All known versions for source package 'swift'
- 2.35.0-2 (sid, trixie)
- 2.30.0-4 (bookworm)
- 2.26.0-10+deb11u1 (bullseye-security, bullseye)