CFE-3294: expose the secret tag and a predicate for it - #6326
Closed
nickanderson wants to merge 3 commits into
Closed
CFE-3294: expose the secret tag and a predicate for it#6326nickanderson wants to merge 3 commits into
nickanderson wants to merge 3 commits into
Conversation
EvalContextVariableGet() always returned the plaintext value, so a caller had no way to ask for a secret-tagged variable to be redacted. Adds a get_secret parameter and *Plaintext wrappers, and moves every existing caller onto the plaintext form. No behaviour change: every call site asks for plaintext, exactly as before. Ticket: CFE-3293 Changelog: None
EvalContextVariableGet() kept the variable's declared type while returning the redacted scalar sentinel, so an indexed read of a secret-tagged container -- mydata[key] -- took the container branch and handed that string to RvalContainerValue(), which aborts with a ProgrammingError. Deriving the type from the value actually being returned fixes it and removes the separate type_out special case. Not reachable yet: no caller passes get_secret=false until the CFE-3294 work. test_secret_container_redacts_indexed_read aborts (SIGABRT) without this and passes with it, and asserts the plaintext reads still work so redaction cannot be faked by breaking container reads. Ticket: CFE-3293 Changelog: None
VARIABLE_TAG_SECRET was a private #define in variable.c, so no code outside that file could ask whether a variable is secret -- which is what every caller that copies a value into a new variable has to do before it can propagate the tag. Moves the constant to variable.h and adds EvalContextVariableIsTaggedSecret() next to EvalContextVariableTags(). Answering via a tag set means allocating one to test a single membership, so this goes straight through VariableResolve(). No behaviour change on its own; the propagation commits that follow use it. Ticket: CFE-3294 Changelog: None
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
VARIABLE_TAG_SECRETwas a private#defineinvariable.c, so no code outsidethat file could ask whether a variable is secret — which is what every caller that
copies a value into a new variable must do before it can propagate the tag.
Moves the constant to
variable.hand addsEvalContextVariableIsTaggedSecret()next to
EvalContextVariableTags(). It resolves the variable directly rather thanbuilding a tag set to test one membership.
No behaviour change on its own; the two propagation PRs stacked on it use it.
Stacked on #6304.