diff options
| author | Greg Hudson <ghudson@mit.edu> | 2013-10-24 12:51:18 -0400 |
|---|---|---|
| committer | Greg Hudson <ghudson@mit.edu> | 2013-10-25 11:36:12 -0400 |
| commit | ec560fac83912abaa15fb158101c8174497081c5 (patch) | |
| tree | f856a161675d836862423520eae35ecd6f1999b4 /src/plugins/locate/python/python.exports | |
| parent | 74c1420ea4dffc1105247e362decf608440751ae (diff) | |
| download | krb5-ec560fac83912abaa15fb158101c8174497081c5.tar.gz krb5-ec560fac83912abaa15fb158101c8174497081c5.tar.xz krb5-ec560fac83912abaa15fb158101c8174497081c5.zip | |
Correctly activate master keys in pre-1.7 KDBs
Starting with 1.7, databases are created with actkvno tl-data in the
K/M entry which gives the initial master key version an activation
time of 0. A database created before 1.7 will not have this tl-data,
but we should behave in the same way as we do for a more recent
database.
Move the actkvno list synthesis code from krb5_dbe_fetch_act_key_list
to krb5_dbe_lookup_actkvno so it applies to kdb5_util commands as well
as libkadm5. Synthesize the same list as we would have initialized
the KDB with, with an activation time of 0 for the earliest master
key.
ticket: 7686
target_version: 1.12
tags: pullup
Diffstat (limited to 'src/plugins/locate/python/python.exports')
0 files changed, 0 insertions, 0 deletions
