qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Justin Ross (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (PROTON-1380) Cyrus SASL accesses strings that have been freed
Date Wed, 04 Jan 2017 16:30:59 GMT

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

Justin Ross updated PROTON-1380:
--------------------------------
    Assignee: Andrew Stitcher

> Cyrus SASL accesses strings that have been freed
> ------------------------------------------------
>
>                 Key: PROTON-1380
>                 URL: https://issues.apache.org/jira/browse/PROTON-1380
>             Project: Qpid Proton
>          Issue Type: Bug
>          Components: proton-c
>    Affects Versions: 0.16.0
>            Reporter: Ted Ross
>            Assignee: Andrew Stitcher
>            Priority: Blocker
>
> If a proton-c user calls pn_sasl_config_name or pn_sasl_config_path, the literal defaults
are replaced with allocated duplicates of the supplied name or path.  When the user's transport
is eventually freed, these allocated strings are also freed (in pn_sasl_free).
> Cyrus SASL retains a global pointer to this freed string and references it the next time
a transport is created.  Since the SASL initialization only occurs once per process, the strings
are not refreshed and the SASL library continues to refer to the freed string.
> There does not appear to be a workaround available for this issue.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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


Mime
View raw message