Bug 893968 - SASL(-1): generic failure: GSSAPI Error: Unspecified GSS failure with 2.1.25
Summary: SASL(-1): generic failure: GSSAPI Error: Unspecified GSS failure with 2.1.25
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: cyrus-sasl
Version: 19
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Petr Lautrbach
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-01-10 11:58 UTC by Marcus Moeller
Modified: 2013-07-29 14:38 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-07-29 14:38:58 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Marcus Moeller 2013-01-10 11:58:58 UTC
Description of problem:
I have upgraded to cyrus-sasl-gssapi-2.1.25-2 and suddenly nslcd stops working. The following error is logged:

nslcd: [16231b] <passwd="..."> failed to bind to LDAP server ldap://lido.d.ethz.ch: Local error: SASL(-1): generic failure: GSSAPI Error: Unspecified GSS failure.  Minor code may provide more information (Server not found in Ke...
nslcd: [16231b] <passwd="..."> DEBUG: ldap_unbind()

With 2.1.23 everything works as expected.

Comment 1 Petr Lautrbach 2013-01-15 15:57:35 UTC
please downgrade and use cyrus-sasl-2.1.23-36.fc18. I unpushed cyrus-sasl-gssapi-2.1.25-2 from Fedora 18 due to abi/api breakage.

This will be fixed in Rawhide soon with rebase to cyrus-sasl-2.1.26.

Comment 2 Fedora End Of Life 2013-04-03 19:38:50 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.

(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19


Note You need to log in before you can comment on or make changes to this bug.