Ankur Tyagi 672ad8f6ad librdkafka: upgrade 2.15.0 -> 2.15.1 ...

Upgrade considerations:

- If you're parsing the nodename as received by connect_cb,
stats_cb, ssl_cert_verify_cb or throttle_cb, make sure you're
correctly parsing it following RFC 3986. Metadata API calls
are unaffected: they return the host and port as separate
fields.
- Make sure the brokers' certificates carry the IP in an
iPAddress entry, not a dNSName entry. Previously the
certificate was validated against dNSName (falling back to the
subject CN) whenever the address could not be parsed as an IP
literal: with OpenSSL < 3.0 or BoringSSL for any IP address,
and on all OpenSSL versions for an IPv6 address configured in
brackets in bootstrap.servers ([::1]:9092), which never
verified. A scoped address (fe80::1%eth0) was likewise
dNSName-matched on every version and now has the zone
stripped before matching. IPv6 addresses ending in :: could
not be connected to at all, as the nodename became host:::port
and failed name resolution. In the remaining cases, a bare
IPv4 or IPv6 literal on OpenSSL >= 3.0, the iPAddress entry
was already used, and behaviour is unchanged.

Changelog:
https://github.com/confluentinc/librdkafka/releases/tag/v2.15.1

Signed-off-by: Ankur Tyagi <ankur.tyagi85@gmail.com>
Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>

2026-09-30 19:09:32 -07:00

..

librdkafka_2.15.1.bb

librdkafka: upgrade 2.15.0 -> 2.15.1

2026-09-30 19:09:32 -07:00