diff options
| author | Sumit Bose <sbose@redhat.com> | 2015-01-15 10:38:33 +0100 |
|---|---|---|
| committer | Jakub Hrozek <jhrozek@redhat.com> | 2015-01-19 11:25:20 +0100 |
| commit | 576ad637181b80d39a4e136c9afbf34c57f76156 (patch) | |
| tree | aa0aa465954ac35d409dcf8481719696ceec23b6 /contrib | |
| parent | 2d5cdfef33dbc8d4a21d6a44676e81501c7af476 (diff) | |
| download | sssd-576ad637181b80d39a4e136c9afbf34c57f76156.tar.gz sssd-576ad637181b80d39a4e136c9afbf34c57f76156.tar.xz sssd-576ad637181b80d39a4e136c9afbf34c57f76156.zip | |
krb5: fix entry order in MEMORY keytab
Since krb5_kt_add_entry() adds new entries at the beginning of a MEMORY
type keytab and not at the end a simple copy into a MEMORY type keytab
will revert the order of the keytab entries. Since e.g. the sssd_krb5
man page give hints about where to add entries into keytab files to help
SSSD to find a right entry we have to keep the order when coping a
keytab into a MEMORY type keytab. This patch fixes this by doing a
second copy to retain the original order.
Resolves https://fedorahosted.org/sssd/ticket/2557
Reviewed-by: Lukáš Slebodník <lslebodn@redhat.com>
Reviewed-by: Jakub Hrozek <jhrozek@redhat.com>
Diffstat (limited to 'contrib')
0 files changed, 0 insertions, 0 deletions