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:34:42 +0100 |
| commit | 7c20e30182e3b5f7f8ebcd8174bded4dcc2f89a8 (patch) | |
| tree | 19491ebb3959a8f8c4608776c19db0fb9670c5ca /src/tests | |
| parent | 6bc93a28d5638ea4e76be699f507a76fa3e357ff (diff) | |
| download | sssd-7c20e30182e3b5f7f8ebcd8174bded4dcc2f89a8.tar.gz sssd-7c20e30182e3b5f7f8ebcd8174bded4dcc2f89a8.tar.xz sssd-7c20e30182e3b5f7f8ebcd8174bded4dcc2f89a8.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>
(cherry picked from commit 24df1487413d13248dcc70d2548a763930da4c65)
Diffstat (limited to 'src/tests')
0 files changed, 0 insertions, 0 deletions