Old stash files are in fact byte order and probably but I'm not sure
word size dependent. Look at the add_mkey command to kdb5_util. I
think if you add a new master key and write it out to a new keytab
format stash file then all should be well.
If the database was created with 1.9.1 then I
Thank you. It turns out I'm a bit of an idiot when I migrated my LDAP
server.
In copying the directory, I managed to leave behind my krbPrincipalKey
values (I used replication, which didn't jive with my extremely
paranoid security settings for that attribute).
THAT said, this would have gone
Old stash files are in fact byte order and probably but I'm not sure
word size dependent. Look at the add_mkey command to kdb5_util. I
think if you add a new master key and write it out to a new keytab
format stash file then all should be well.
If the database was created with 1.9.1 then I
Thank you. It turns out I'm a bit of an idiot when I migrated my LDAP
server.
In copying the directory, I managed to leave behind my krbPrincipalKey
values (I used replication, which didn't jive with my extremely
paranoid security settings for that attribute).
THAT said, this would have gone
Public bug reported:
Running 11.10 (Oneiric). Additional specifications in tags. This
appears to apply to libkdb5-5 version 1.9.1+dfsg-1ubuntu2.2.
I have copied a working LDAP-backed KDC configuration from a 64-bit EC2
instance into a 32-bit EC2 instance (the binaries are installed fresh).
Public bug reported:
Running 11.10 (Oneiric). Additional specifications in tags. This
appears to apply to libkdb5-5 version 1.9.1+dfsg-1ubuntu2.2.
I have copied a working LDAP-backed KDC configuration from a 64-bit EC2
instance into a 32-bit EC2 instance (the binaries are installed fresh).
