[
https://issues.apache.org/jira/browse/PROTON-1380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15798977#comment-15798977
]
Andrew Stitcher commented on PROTON-1380:
-----------------------------------------
Yep, looks like we need to copy these strings again before giving them to
cyrus. Possibly keeping a static buffer to hold them, might avoid possible
warnings from valgrind (but sizing the buffer may be tricky).
> 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: [email protected]
For additional commands, e-mail: [email protected]
