[
https://issues.apache.org/jira/browse/PROTON-950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14652380#comment-14652380
]
Andrew Stitcher edited comment on PROTON-950 at 8/3/15 8:00 PM:
----------------------------------------------------------------
@gsim unless you've manually set the flag somehow for the messenger code this
is expected as there is no code committed yet to do this automatically for
messenger (else this repoort would already have been resolved!). All that is
committed currently is the sasl level code for the option itself.
[Edit: The hold up, is that adding that code to messenger causes valgrind
errors on the Travis CI box which I can't exactly replicate. So I can't see
whether it is safe just to suppress them]
was (Author: astitcher):
@gsim unless you've manually set the flag somehow for the messenger code this
is expected as there is no code committed yet to do this automatically for
messenger (else this repoort would already have been resolved!). All that is
committed currently is the sasl level code for the option itself.
> SASL PLAIN over cleartext should be supported
> ---------------------------------------------
>
> Key: PROTON-950
> URL: https://issues.apache.org/jira/browse/PROTON-950
> Project: Qpid Proton
> Issue Type: Bug
> Components: proton-c
> Affects Versions: 0.10
> Reporter: Ted Ross
> Assignee: Andrew Stitcher
> Priority: Blocker
> Fix For: 0.10
>
>
> In the current 0.10 alpha, if SASL PLAIN is selected, it will only work if
> the connection is encrypted (using SSL). This is a surprising change of
> behavior from earlier versions of Proton and it's arguable that a security
> policy like that should be left to the application using the Proton library.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
