profiles: tor: add memory-deny-write-execute #6641
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
kmk3
approved these changes
Feb 5, 2025
Tested by running tor (as a client) for more than 7 hours with continuous traffic. Note: Not tested as a relay.
1319ec1 to
3d3b265
Compare
|
Merged, thanks! |
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.
Add
memory-deny-write-executeto tor profile. (Tested by running tor for more than 7 hour with continuous traffic.)Note: not tested as relay. If it is expected that tor touches on this only as a relay, then it would benefit to await a second opinion.
Update: tor ran (as client) for 7+ hours continuously without issue.