Conditionally add interface proxies for taint persistence #20
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
If we always load the proxies and do not use the taint persistence driver, which might be the sensible path due to performance/compatibility restrictions the application will break. As the focus is not purely on GDPR tainting anymore, the addition of the problematic proxies is hidden behind a flag has has to be passed to the agent. It would be nicer to dynamically detect this, but this a) might be slow and b) is fairly complex.
leeN
added
enhancement
tmbrbr
approved these changes
Feb 24, 2024
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.
If we always load the proxies and do not use the taint persistence driver, which might be the sensible path due to
performance/compatibility restrictions the application will break.
As the focus is not purely on GDPR tainting anymore, the addition of the problematic proxies is hidden behind a flag has has to be passed to the agent.
It would be nicer to dynamically detect this, but this a) might be slow and b) is fairly complex.