On 8.02.14 18:41, Roberto C. Sánchez wrote:
>
> I am going through all the old bugs against cyrus-sasl2, and I wanted to
> see if you had any more information on this. I did a little
> investigating, and I found this in the saslauthd source code
> (auth_krb5.c):
>
> if (config) {
>
On Mon, Apr 27, 2009 at 05:15:54PM +0200, Friedemann Stoyan wrote:
> Roberto C. Sánchez wrote:
>
> >Is it being set in the init script prior to the defaults file being
> >read?
>
> No. In general there is no need to set KRB5_KTNAME. If it is unset
> the default (/etc/krb5.keytab) is used. But not
Roberto C. Sánchez wrote:
Is it being set in the init script prior to the defaults file being
read?
No. In general there is no need to set KRB5_KTNAME. If it is unset the default
(/etc/krb5.keytab) is used. But not from saslauthd.
Regards
Friedemann
--
To UNSUBSCRIBE, email to debian-bug
On Mon, Apr 27, 2009 at 10:51:07AM +0200, Friedemann Stoyan wrote:
> On 27.04.09 00:16, Russ Allbery wrote:
>
> > Do you have KRB5_KTNAME set in the environment before running the init
> > script for some reason?
>
> No, I haven't.
>
Is it being set in the init script prior to the defaults file
On 27.04.09 00:16, Russ Allbery wrote:
> Friedemann Stoyan writes:
>
> > when using saslauthd with kerberos5 authentication mechanism it simply
> > fails with:
> > "saslauthd[10678]: do_auth: auth failure: [user=xxx] [service=ldap]
> > [realm=x] [mech=kerberos5] [reason=saslauthd int
Friedemann Stoyan writes:
> when using saslauthd with kerberos5 authentication mechanism it simply
> fails with:
> "saslauthd[10678]: do_auth: auth failure: [user=xxx] [service=ldap]
> [realm=x] [mech=kerberos5] [reason=saslauthd internal error]"
>
> Fix:
> Explicitly set the environ
Package: sasl2-bin
Version: 2.1.22.dfsg1-23
Severity: minor
Dear Maintainers,
when using saslauthd with kerberos5 authentication mechanism it simply fails
with:
"saslauthd[10678]: do_auth: auth failure: [user=xxx] [service=ldap]
[realm=x] [mech=kerberos5] [reason=saslauthd internal
7 matches
Mail list logo
