Debian Patches
Status for python-oslo.messaging/17.3.0-4
| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| no-functional-test.patch | Disable some functional tests We don't really care about zmq for the moment. | Thomas Goirand <zigo@debian.org> | not-needed | 2018-08-20 | ||
| fix-not-using-non-durable.patch | Fix not using non-durable | Thomas Goirand <zigo@debian.org> | no | 2026-02-25 | ||
| install-missing-files.patch | install all files | Thomas Goirand <zigo@debian.org> | no | 2026-02-25 | ||
| CVE-2026-44393_OSSN-0096_Fix_RabbitMQ_TLS_hostname_verification.patch | CVE-2026-44393 / OSSN-0096:Fix RabbitMQ TLS hostname verification When TLS is used with ssl_ca_file, the Rabbit driver validates the certificate chain but does not verify the broker hostname. This could allow a MITM attacker with a certificate trusted by the deployment CA to impersonate the RabbitMQ broker. . This change adds ssl_enforce_hostname_verification. When enabled together with ssl_ca_file, the driver enables hostname verification. . For single-broker configurations, the broker hostname is passed explicitly. For multi-broker configurations, Kombu >= 5.2.0 is required when hostname verification is enforced. Older Kombu versions will result in an explicit failure instead of silently disabling verification. . NOTE: Unlike master, the backport keeps ssl_enforce_hostname_verification disabled by default to preserve stable branch behavior compatibility. =================================================================== |
Daniel Bengtsson <dbengt@redhat.com> | yes | debian upstream | upstream, https://review.opendev.org/c/openstack/oslo.messaging/+/988979 | 2026-06-01 |
All known versions for source package 'python-oslo.messaging'
- 17.3.0-4 (forky, sid)
- 16.1.0-3+deb13u1 (trixie-security, trixie-proposed-updates)
- 16.1.0-3 (trixie)
- 14.0.3-0+deb12u1 (bookworm-security, bookworm-proposed-updates)
- 14.0.0-2 (bookworm)