You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Andrew Stitcher (JIRA)" <ji...@apache.org> on 2016/04/22 22:35:12 UTC

[jira] [Commented] (PROTON-574) proton-c: Messenger doesn't indicate when connection is aborted for a SASL negotation failure

    [ https://issues.apache.org/jira/browse/PROTON-574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15254612#comment-15254612 ] 

Andrew Stitcher commented on PROTON-574:
----------------------------------------

Since 0.10 was released and the SASL code changed a lot I don't think these patches will apply any more. And perhaps may no longer be necessary.

> proton-c: Messenger doesn't indicate when connection is aborted for a SASL negotation failure
> ---------------------------------------------------------------------------------------------
>
>                 Key: PROTON-574
>                 URL: https://issues.apache.org/jira/browse/PROTON-574
>             Project: Qpid Proton
>          Issue Type: Bug
>          Components: proton-c
>    Affects Versions: 0.7
>            Reporter: Dominic Evans
>            Assignee: Andrew Stitcher
>              Labels: messenger, patch
>         Attachments: 05_return_sasl_auth_errors_messenger.c.patch, 05_return_sasl_auth_errors_transport.c.patch, 05_return_sasl_auth_errors_transport.h.patch
>
>
> Currently if a Messenger's connection is aborted at the remote end, there's no differentiation between the connection just being dropped and a failure to negotiate SASL.



--
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