[
https://issues.apache.org/jira/browse/PROTON-975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14681983#comment-14681983
]
ASF subversion and git services commented on PROTON-975:
--------------------------------------------------------
Commit daba85301f0cf785ae07bf5f1ba1a580736c88cb in qpid-proton's branch
refs/heads/0.10.x from [~astitcher]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=daba853 ]
PROTON-975: Fix to ensure that we switch to decrypting incoming frames early
enough
> connecting with DIGEST-MD5 fails if buffer containing outcome and first
> encrypted frame is received
> ---------------------------------------------------------------------------------------------------
>
> Key: PROTON-975
> URL: https://issues.apache.org/jira/browse/PROTON-975
> Project: Qpid Proton
> Issue Type: Bug
> Components: proton-c
> Affects Versions: 0.10
> Reporter: Ken Giusti
> Assignee: Andrew Stitcher
> Priority: Blocker
> Fix For: 0.10.1
>
> Attachments: send.py
>
>
> I'm hitting an occasional client crash when using an DIGEST-MD5 SASL mech to
> talk to the qpidd broker.
> I've built the broker using the 0.10rc1 as the proton library.
> I'm using a pyngus based client. I will upload this reproducer.
> Best I can tell, the client pushes a single buffer to the transport that
> contains both the SASL outcome frame from qpidd and the first encrypted
> frame. SASL does not handle this case correctly and attempts to parse the
> encrypted frame as cleartext.
> I will open another bug against the frame decode to prevent parsing invalid
> frames.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
