kata: enable blocking logs access #1193
Merged
Conversation
This file contains 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
|
burgerdev
force-pushed
the
burgerdev/logs
branch
from
0f1562e to
633e573
Compare
katexochen
approved these changes
Jan 31, 2025
burgerdev
force-pushed
the
burgerdev/logs
branch
from
633e573 to
2756fad
Compare
burgerdev
force-pushed
the
burgerdev/logs
branch
from
2756fad to
8b6e044
Compare
katexochen
approved these changes
Jan 31, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Access to logs can now be blocked by policy with an adjustment to the settings, see https://docs.edgeless.systems/contrast/architecture/security-considerations#logs.
Logs access is still allowed by default.