You are viewing a plain text version of this content. The canonical link for it is here.

Posted to proton@qpid.apache.org by "Andrew Stitcher (JIRA)" <ji...@apache.org> on 2016/02/15 22:34:18 UTC

[jira] [Resolved] (PROTON-988) pn_messenger_set_flags does not support new SASL flag correctly

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

Andrew Stitcher resolved PROTON-988.
------------------------------------
       Resolution: Fixed
    Fix Version/s: 0.13.0

I've fixed the blatant issue here, but I've not made the API any more sensible. And I didn't add any tests for this API as there is no sensible place to do it currently!

> pn_messenger_set_flags does not support new SASL flag correctly
> ---------------------------------------------------------------
>
>                 Key: PROTON-988
>                 URL: https://issues.apache.org/jira/browse/PROTON-988
>             Project: Qpid Proton
>          Issue Type: Bug
>          Components: proton-c
>    Affects Versions: 0.10
>         Environment: All OS
>            Reporter: Clemens Vasters
>            Assignee: Andrew Stitcher
>              Labels: messenger
>             Fix For: 0.13.0
>
>
> The new flag PN_FLAGS_ALLOW_INSECURE_MECHS cannot be set though pn_messenger_set_flags.
> Setting the other defined flag, PN_FLAGS_CHECK_ROUTES, causes the preset PN_FLAGS_ALLOW_INSECURE_MECHS to be irrecoverably overridden.



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