Debian Patches
Status for python-oslo.messaging/14.0.3-0+deb12u1
| 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 | ||
| Implement_get_rpc_client_function.patch | Implement get_rpc_client function We already expose functions to handle the instantiation of classes such as RPCServer and RPCTransport but the same was never done for RPCClient so the API is inconsistent in its enforcement. This adds a get_rpc_client function that should be used instead of instatiating the RPCClient class directly to be more consistent. This also allows to handle more logic inside the function in the future such as if implementations for an async client is implemented, as investigation in [1] has shown. [1] https://review.opendev.org/c/openstack/oslo.messaging/+/858936 |
Tobias Urdin <tobias.urdin@binero.com> | no | 2022-10-22 | ||
| Support_overriding_class_for_get_rpc_helper_functions.patch | Support overriding class for get_rpc_* helper functions We currently do not support overriding the class being instantiated in the RPC helper functions, this adds that support so that projects that define their own classes that inherit from oslo.messaging can use the helpers. For example neutron utilizes code from neutron-lib that has it's own RPCClient implementation that inherits from oslo.messaging, in order for them to use for example the get_rpc_client helper they need support to override the class being returned. The alternative would be to modify the internal _manual_load variable which seems counter-productive to extending the API provided to consumers. |
Tobias Urdin <tobias.urdin@binero.se> | no | 2023-01-12 | ||
| CVE-2026-44393_OSSN-0096_Fix_RabbitMQ_TLS_hostname_verification.patch | [PATCH] 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. . Conflicts: oslo_messaging/tests/drivers/test_impl_rabbit.py . Resolved conflict caused by remaining unit tests for FIPS mode support. =================================================================== |
Daniel Bengtsson <dbengt@redhat.com> | yes | debian upstream | upstream, https://review.opendev.org/c/openstack/oslo.messaging/+/988981 | 2026-06-04 |
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)