Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SASL GSSAPI mechanism acceptor wrongly returns zero maxbufsize #402

Closed
brong opened this issue Oct 21, 2015 · 4 comments
Closed

SASL GSSAPI mechanism acceptor wrongly returns zero maxbufsize #402

brong opened this issue Oct 21, 2015 · 4 comments

Comments

@brong
Copy link
Member

brong commented Oct 21, 2015

From: Sergio Gelato
Bugzilla-Id: 3912
Version: 2.1.x
Owner: Alexey Melnikov

@brong
Copy link
Member Author

brong commented Oct 21, 2015

Attachment-Id: 1560
From: Sergio Gelato
Type: text/plain
File: 06260404c047e111f86b67de2862ec124f8fe2ec.patch

Postpone computing maxbufsize until after security layers have been set

@whm
Copy link

whm commented Mar 21, 2017

I started seeing this problem on my Xenial OpenLDAP server last night. The error was:

slapd[22083]: encoded packet size too big (67871 > 65536)

Applying this patch to the Xenial build of Cyrus SASL has resolved the issue. The exact version is: 2.1.26.dfsg1-14build1.

@tobyblake
Copy link

Hello, just a me-too to say that we saw this issue with machines upgraded to Scientific Linux 7 (from SL6) and the patch included here does seem to fix the issue for us. It would be good if it could be included in the next release.

ksmurchison added a commit that referenced this issue Jul 13, 2017
@ksmurchison
Copy link
Contributor

Fixed with 6f8cc36

brong pushed a commit that referenced this issue Jan 29, 2018
brong pushed a commit that referenced this issue Jan 30, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants