qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robbie Gemmell (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (PROTON-1620) TLS / SSL thread safety with proactor
Date Mon, 30 Oct 2017 17:57:00 GMT

     [ https://issues.apache.org/jira/browse/PROTON-1620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Robbie Gemmell updated PROTON-1620:
    Fix Version/s:     (was: proton-c-0.19.0)

This JIRA had changes against it included in 0.18.0, and now has some more against it on master/potentially-0.18.1,
but remains open and is only marked fix for 0.19.0.

I'm changing the fix-version to 0.18.1. If its done, please resolve it. If there are further
changes to come, make them or raise a new JIRA for 0.19.0 and rename/redescribe this one as
needed to cover the changes made.

> TLS / SSL thread safety with proactor
> -------------------------------------
>                 Key: PROTON-1620
>                 URL: https://issues.apache.org/jira/browse/PROTON-1620
>             Project: Qpid Proton
>          Issue Type: Bug
>          Components: proton-c
>    Affects Versions: proton-c-0.18.0
>            Reporter: Cliff Jansen
>            Assignee: Alan Conway
>            Priority: Critical
>             Fix For: proton-c-0.18.1
> ssl_domain objects are semi-global.
> For example two connections simultaneously creating or releasing their own private pn_ssl_t
objects may mess up the refcount of the shared pn_ssl_domain_t object leading to memory corruption
or leaks.
> Windows schannel is further complicated by the OS internal refcounting of its security
context thingies.  That may get automatically solved by the above, or may require a separate
JIRA to track.  The same may apply to openssl.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org

View raw message