Remove trust quorum shares from sled agent requests #1375
Merged
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.
The primary motivator behind this was to avoid accidentally logging all the trust quorum shares from RSS, so we include some relatively heavy-handed machinery to minimize the chances of reintroducing that in the future.
There are two structural changes here that I believe are correct regardless of the logging issue:
SledAgentRequest. It's still sent alongsideSledAgentRequestwhen RSS initializes a remote sled, but not as part of the same structure.If you think the avoidance of
#[derive(Serialize)]and the use of thedanger_serialize_*functions is overboard, I'm certainly not wedded to them, but I think they're a reasonable starting point for discussion in terms of avoiding accidentally reintroducing leakage of the shares.