[16930] in Kerberos-V5-bugs
[krbdev.mit.edu #9120] [Comment] profile final flag limitations
daemon@ATHENA.MIT.EDU (Greg Hudson via RT)
Sun Apr 14 10:24:48 2024
From: "Greg Hudson via RT" <rt-comment@kerborg-prod-app-1.mit.edu>
In-Reply-To: <rt-4.4.3-2-1528752-1712955432-1153.9120-8-0@kerborg-prod-app-1.mit.edu>
Message-ID: <rt-4.4.3-2-1759841-1713104681-1798.9120-8-0@kerborg-prod-app-1.mit.edu>
To: "AdminCc of krbdev.mit.edu Ticket #9120":;
Date: Sun, 14 Apr 2024 10:24:41 -0400
MIME-Version: 1.0
Reply-To: rt-comment@kerborg-prod-app-1.mit.edu
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: krb5-bugs-bounces@mit.edu
http://kerborg-prod-app-1.mit.edu/rt/Ticket/Display.html?id=9120
This is a comment. It is not sent to the Requestor(s):
Another note: whlie the syntax and data model can naturally accommodate an
empty section or subsection with the final flag set, neither can naturally
represent a final-flagged relation with no values. (In the memory
representation, a node with the deleted and final flags set could possibly do
in a pinch, but it isn't a natural representation. A node with a null value
is semantically a section, not a relation.)
So, even with the two numbered limitations above addressed, there is no way to
use the final flag to force the use of the default value for a variable, or to
force an empty list for a relation that can have multiple values.
_______________________________________________
krb5-bugs mailing list
krb5-bugs@mit.edu
https://mailman.mit.edu/mailman/listinfo/krb5-bugs
