Kerberos 5 is configured for an OpenSuse machine.
Login always fails for normal users except for 'root'
(/bin/login should be used instead of the version of
kerberized login.krb5 shipped with K5 installation
package. But the following message shows that this
/bin/login is kerberized since it reports kerberos
authentication failure upon linux login.). The
krb5kdc.log looks ok. But there is some error message
in syslog.

Jun 26 10:32:03 mymachine krb5kdc[14079](info): AS_REQ
(7 etypes {18 17 16 23 1 3 2}) ISSUE:
authtime 1182871923, etypes {rep=16 tkt=16 ses=16},

Jun 26 09:59:10 mymachine kdm: :1[14582]:
pam_krb5[14582]: authentication fails for 'tester'
(tester@MYDOMAIN): Authentication failure (Decrypt
integrity check failed)

'tester' is added both as a local user and as a
principal in kerberos. 'tester' can logon w/o problem
before K5 is installed. The problem appears when logon
locally on the machine as 'tester' or other normal

>From the pam_krb5 error message, some googled results

suggest this:



You might have an invalid ticket.

Verify both of these conditions:


Make sure that your credentials are valid.
Destroy your tickets with kdestroy, and create new
tickets with kinit.

Make sure that the target host has a keytab file
with the correct version of the service key. Use
kadmin to view the key version number of the service
principal (for example, host/FQDN-hostname) in the
Kerberos database. Also, use klist -k on the target
host to make sure that it has the same key version

So, from this, I used the following commands to varify
if principals use the same key as 'host' of master

After check with the command 'klist -k' it shows:

KVNO Principal
3 host/mymachine@MYDOMAIN
3 host/mymachine@MYDOMAIN

Then, run 'kadmin.local:get_principal host/mymachine
Principal: host/mymachine@MYDOMAIN
Expiration date: [never]
Last password change: Tue Jun 26 09:58:41 CDT 2007
Password expiration date: [none]
Maximum ticket life: 1 day 00:00:00
Maximum renewable life: 0 days 00:00:00
Last modified: Tue Jun 26 09:58:41 CDT 2007
Last successful authentication: [never]
Last failed authentication: [never]
Failed password attempts: 0
Number of keys: 2
Key: vno 3, Triple DES cbc mode with HMAC/sha1, no
Key: vno 3, DES cbc mode with CRC-32, no salt
Policy: [none]

So, it seems ok(?). The error messages seems to me
that there is some discrepancy between service key of
master kdc and the one used for principal? But to
ensure everything is ok, this is the order:
- create host/mymachine@MYDOMAIN principal
- extract host keytab for above principal to
- add principal for 'tester'

Any thoughts? Thanks

__________________________________________________ __________________________________
Don't pick lemons.
See all the new 2007 cars at Yahoo! Autos.