[16934] in Kerberos-V5-bugs
[krbdev.mit.edu #9118] git commit
daemon@ATHENA.MIT.EDU (Greg Hudson via RT)
Sat Apr 20 20:51:09 2024
From: "Greg Hudson via RT" <rt@krbdev.mit.edu>
In-Reply-To:
Message-ID: <rt-4.4.3-2-2776012-1713660662-1889.9118-5-0@mit.edu>
To: "AdminCc of krbdev.mit.edu Ticket #9118":;
Date: Sat, 20 Apr 2024 20:51:02 -0400
MIME-Version: 1.0
Reply-To: rt@krbdev.mit.edu
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: krb5-bugs-bounces@mit.edu
<URL: https://krbdev.mit.edu/rt/Ticket/Display.html?id=9118 >
Do not reload a modified profile data object
The profile library normally attempts to reload a profile data tree if
the backing file has changed. Reloading a dirty profile object
discards any modifications made by the caller. If we assume that the
modifications are destined to be flushed back out to the backing file,
then there is no good answer--one or the other set of changes will be
lost. But the caller may have a different intended use for the
modified tree (profile_flush_to_file(), profile_flush_to_buffer(),
krb5_init_context_profile()), for which the caller's modifications may
be critical. Avoid discarding in-memory edits to ensure the
correctness of these use cases.
https://github.com/krb5/krb5/commit/9b2fb80ad24006784170875709a04dc79e03b401
Author: Greg Hudson <ghudson@mit.edu>
Commit: 9b2fb80ad24006784170875709a04dc79e03b401
Branch: master
src/util/profile/prof_file.c | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
_______________________________________________
krb5-bugs mailing list
krb5-bugs@mit.edu
https://mailman.mit.edu/mailman/listinfo/krb5-bugs
