You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@armanjupriya-er did you try to modify the code and see if it can be smoothly upgrade? Any report on upgrading can help the upstream to handle this issue. Otherwise, you're waiting someone find spare time to figure out all the details by themseleves.
We've met this issue with a customer, whose network does deep packet inspection and somehow prevents TLSv1.2 connections to successfully do handshake. As 1.2 usage is hardcoded, pulsar connection was no longer possible from there. I've opened a PR (#529) and would be happy to get it evaluated to be incorporated in pulsar-client (we use python package).
Activity
manju-priya-ar commentedon May 12, 2023
@BewareMyPower : Any plans to support TLS 1.3 in near future release?
BewareMyPower commentedon May 12, 2023
Sorry. There is no plan recently.
tisonkun commentedon Jun 13, 2023
@armanjupriya-er did you try to modify the code and see if it can be smoothly upgrade? Any report on upgrading can help the upstream to handle this issue. Otherwise, you're waiting someone find spare time to figure out all the details by themseleves.
ciuncan commentedon Dec 10, 2025
We've met this issue with a customer, whose network does deep packet inspection and somehow prevents TLSv1.2 connections to successfully do handshake. As 1.2 usage is hardcoded, pulsar connection was no longer possible from there. I've opened a PR (#529) and would be happy to get it evaluated to be incorporated in
pulsar-client(we use python package).