> I think we can chock this up to operator error due to flaky DNS - why it
> worked ~25% of the time is a mystery... krb is pretty sensitive to forward,
> reverse, and canonical host names.
>
> Thanks... looks like 'tis time to update more machines now :)
Just to clarify - you consider this bug to
On 11/06/11 18:45 -0700, Richard A Nelson wrote:
On Sat, 11 Jun 2011, Dan White wrote:
Yes, interestingly, this shows up for both failure modes:
Jun 11 15:37:02 sparks-ave ldapwhoami: canonuserfunc error -7
Jun 11 15:37:02 sparks-ave ldapwhoami: _sasl_plugin_load failed on
On Sat, 11 Jun 2011, Dan White wrote:
Yes, interestingly, this shows up for both failure modes:
Jun 11 15:37:02 sparks-ave ldapwhoami: canonuserfunc error -7
Jun 11 15:37:02 sparks-ave ldapwhoami: _sasl_plugin_load failed on
sasl_canonuser_init for plugin:
On 11/06/11 10:54 -0700, Richard A Nelson wrote:
$ ldapwhoami
SASL/GSSAPI authentication started
ldap_sasl_interactive_bind_s: Invalid credentials (49)
additional info: SASL(-13): authentication failure: GSSAPI Failure:
gss_accept_sec_context
$ ldapwhoami
SASL/GSSAPI authentication started
On Sat, 11 Jun 2011, Dan White wrote:
Do you have libsasl2-modules-gssapi-mit or libsasl2-modules-gssapi-heimdal
installed, and what version?
ii libsasl2-modules-gssapi-heimdal 2.1.24~rc1.dfsg1+cvs2011-05-23-4
Is your slapd running on a separate host?
No, 'tis using ldapi://
If so, is i
On 11/06/11 10:54 -0700, Richard A Nelson wrote:
$ ldapwhoami
SASL/GSSAPI authentication started
ldap_sasl_interactive_bind_s: Invalid credentials (49)
additional info: SASL(-13): authentication failure: GSSAPI Failure:
gss_accept_sec_context
$ ldapwhoami
SASL/GSSAPI authentication starte
$ ldapwhoami
SASL/GSSAPI authentication started
ldap_sasl_interactive_bind_s: Invalid credentials (49)
additional info: SASL(-13): authentication failure: GSSAPI Failure:
gss_accept_sec_context
$ ldapwhoami
SASL/GSSAPI authentication started
SASL username: cowboy@
SASL SSF: 56
SASL data se
7 matches
Mail list logo