[
https://issues.apache.org/jira/browse/PROTON-933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14615592#comment-14615592
]
ASF subversion and git services commented on PROTON-933:
--------------------------------------------------------
Commit c6499b687cce4102655db2d7012bc7cbc9bcd1fd in qpid-proton's branch
refs/heads/master from [~astitcher]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=c6499b6 ]
PROTON-933: Workaround for seeming bug in Cyrus SASL GSSAPI buffer size
reporting
> Cyrus SASL GSSAPI plugin can error if sent long buffers.
> --------------------------------------------------------
>
> Key: PROTON-933
> URL: https://issues.apache.org/jira/browse/PROTON-933
> Project: Qpid Proton
> Issue Type: Bug
> Components: proton-c
> Affects Versions: 0.10
> Reporter: Andrew Stitcher
> Assignee: Andrew Stitcher
> Priority: Blocker
>
> Cyrus SASL GSSAPI is not able to handle buffers in the advertised way -
> Even if you limit the amount of data to decode on the server side to the
> SASL_MAXOUTBUF value that it reports it can fail with a syslog of (for
> example):
> {quote}
> Jul 6 13:32:38 proton msgr-recv: encoded packet size too big (32828 > 32768)
> {quote}
> It appears that the decode routine can coalesce received buffers, and in fact
> its actual requirement is that you may not _encode_ on the _client_ any more
> than the value returned on the server. However the value of SASL_MAXOUTBUF
> that is returned on the client is 60 bytes bigger than the value returned on
> the server.
> The workaround is to subract 60 bytes from the value on the returned on the
> client before using it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
