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 2015/07/06 22:30:04 UTC
[jira] [Resolved] (PROTON-933) Cyrus SASL GSSAPI plugin can error
if sent long buffers.
[ https://issues.apache.org/jira/browse/PROTON-933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Stitcher resolved PROTON-933.
------------------------------------
Resolution: Fixed
Fix Version/s: 0.10
> 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
> Fix For: 0.10
>
>
> 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)