Ticket History #9014: Using locking in MEMORY krb5_cc_get_principal()

Using locking in MEMORY krb5_cc_get_principal()

Without locking, the principal pointer could be freed out from under
krb5_copy_principal() by another thread calling krb5_cc_initialize()
or krb5_cc_destroy().

(cherry picked from commit 1848447291c68e21311f441b0458ae53471d00d3)

https://github.com/krb5/krb5/commit/5cf95e57e1a45f20d6ae1ea8232c1511f4b1940b
Author: Greg Hudson <ghudson@mit.edu>
Commit: 5cf95e57e1a45f20d6ae1ea8232c1511f4b1940b
Branch: krb5-1.19
src/lib/krb5/ccache/cc_memory.c | 17 +++++++++++------
1 files changed, 11 insertions(+), 6 deletions(-)

Using locking in MEMORY krb5_cc_get_principal()

Without locking, the principal pointer could be freed out from under
krb5_copy_principal() by another thread calling krb5_cc_initialize()
or krb5_cc_destroy().

(cherry picked from commit 1848447291c68e21311f441b0458ae53471d00d3)

https://github.com/krb5/krb5/commit/4abb051f76ae8f55247875a68f424a62a6315ec0
Author: Greg Hudson <ghudson@mit.edu>
Commit: 4abb051f76ae8f55247875a68f424a62a6315ec0
Branch: krb5-1.18
src/lib/krb5/ccache/cc_memory.c | 17 +++++++++++------
1 files changed, 11 insertions(+), 6 deletions(-)