-
Notifications
You must be signed in to change notification settings - Fork 249
vminitd: Scrub envvars printed in debug log #521
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Draft
dcantah
wants to merge
1
commit into
apple:main
Choose a base branch
from
dcantah:vminitd-log-scrub
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,66 @@ | ||
| //===----------------------------------------------------------------------===// | ||
| // Copyright © 2026 Apple Inc. and the Containerization project authors. | ||
| // | ||
| // Licensed under the Apache License, Version 2.0 (the "License"); | ||
| // you may not use this file except in compliance with the License. | ||
| // You may obtain a copy of the License at | ||
| // | ||
| // https://www.apache.org/licenses/LICENSE-2.0 | ||
| // | ||
| // Unless required by applicable law or agreed to in writing, software | ||
| // distributed under the License is distributed on an "AS IS" BASIS, | ||
| // WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. | ||
| // See the License for the specific language governing permissions and | ||
| // limitations under the License. | ||
| //===----------------------------------------------------------------------===// | ||
|
|
||
| import ContainerizationOCI | ||
|
|
||
| /// Redacts environment variable values from a list of env vars in "KEY=VALUE" format. | ||
| /// Returns the env vars with values replaced by "<redacted>". | ||
| func redactEnvValues(_ env: [String]) -> [String] { | ||
| env.map { entry in | ||
| if let equalsIndex = entry.firstIndex(of: "=") { | ||
| let key = entry[..<equalsIndex] | ||
| return "\(key)=<redacted>" | ||
| } | ||
| return entry | ||
| } | ||
| } | ||
|
|
||
| /// A log-safe representation of a Process that redacts environment variable values. | ||
| struct RedactedProcess: CustomStringConvertible { | ||
| let process: ContainerizationOCI.Process | ||
|
|
||
| var description: String { | ||
| var copy = process | ||
| copy.env = redactEnvValues(copy.env) | ||
| return "\(copy)" | ||
| } | ||
| } | ||
|
|
||
| /// A log-safe representation of a Spec that redacts environment variable values. | ||
| struct RedactedSpec: CustomStringConvertible { | ||
| let spec: ContainerizationOCI.Spec | ||
|
|
||
| var description: String { | ||
| var copy = spec | ||
| if var process = copy.process { | ||
| process.env = redactEnvValues(process.env) | ||
| copy.process = process | ||
| } | ||
| return "\(copy)" | ||
| } | ||
| } | ||
|
|
||
| extension ContainerizationOCI.Spec { | ||
| var redacted: RedactedSpec { | ||
| RedactedSpec(spec: self) | ||
| } | ||
| } | ||
|
|
||
| extension ContainerizationOCI.Process { | ||
| var redacted: RedactedProcess { | ||
| RedactedProcess(process: self) | ||
| } | ||
| } | ||
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
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.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Question: I was reading the Docker Compose secrets docs and wondered, should we adopt a policy of never logging any env/argv values (even at debug), that is always redact env + args/commandLine? Or is the intent to only redact env and leave argv visible for debugging?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good question. We should clearly understand where app secret values could be stored at rest:
.envfiles or anything similar - these are owned by the user socontainerhas no responsibility for them.Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yeah, I agree w/ the boot logs part which are written today by default. As you said gate boot logs and if I'm thinking it right;
(1) dont set
config.bootLog = BootLog.file(...)by default(2) only write boot logs if the user explicitly asks?
(3) move sensitive guest logs to trace by making the spec/argv logs trace-level.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should emit boot logs always, it's too useful for diagnostics. I think John meant redact the container configs in them entirely possibly
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ahh, I see what you mean. yeah, config only redaction will be a balanced approach.