[
https://issues.apache.org/jira/browse/PROTON-969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14649352#comment-14649352
]
Andrew Stitcher commented on PROTON-969:
----------------------------------------
This is true, but not all that relevant to this bug per se.
Ted's point (I think) is just that the Proton-C code violates the constraints
defined by the man page.
The actual Cyrus implementation (at least as of 2.1.25) has a counter for the
server and the client init and indeed you need to call
sasl_client_done()/sasl_server_done() once for each time you call client/server
init for cyrus to do its cleanup.
However if you don't do this the worst that can happen is that cyrus leaks
memory and that wouldn't be a blocker to the 0.10 release (IMO)
> Cyrus SASL module calls sasl_server_init once for every incoming connection
> ---------------------------------------------------------------------------
>
> Key: PROTON-969
> URL: https://issues.apache.org/jira/browse/PROTON-969
> Project: Qpid Proton
> Issue Type: Bug
> Components: proton-c
> Reporter: Ted Ross
> Assignee: Andrew Stitcher
> Fix For: 0.10
>
>
> The Cyrus SASL module invokes sasl_server_init once for every incoming
> connection on a listener. The Manpage for sasl_server_init states that it
> should be called only once per process.
> Is this a blocker for 0.10?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
