-
Notifications
You must be signed in to change notification settings - Fork 187
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
feat: add IPv6 obfuscation to cleaner #4362
Merged
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
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #4362 +/- ##
==========================================
+ Coverage 77.32% 77.34% +0.02%
==========================================
Files 745 745
Lines 41498 41548 +50
Branches 8816 8824 +8
==========================================
+ Hits 32087 32137 +50
+ Misses 8364 8363 -1
- Partials 1047 1048 +1
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
c63a1e2
to
7ccf21f
Compare
JoySnow
approved these changes
Feb 24, 2025
c23199d
to
49d3c17
Compare
JoySnow
reviewed
Feb 25, 2025
JoySnow
approved these changes
Feb 25, 2025
87a25b9
to
1035551
Compare
test me |
- Add IPv6 obfuscation, and generate relevant reports. IPv6 Obfuscation should keep the length of the original address after obfuscating. One IPv6 address, no matter compressed or exploded will be treat as one same address, hence has the same obfuscated result. - IPv6 obfuscation will be enabled individually by setting "obfuscate_ipv6=True" in insights-client.conf. And can be disabled for particular specs by adding "no_obfuscate=['ipv6']" in spec RegistryPoint - RHINENG-14804 Signed-off-by: Xiangce Liu <[email protected]>
Signed-off-by: Xiangce Liu <[email protected]>
Signed-off-by: Xiangce Liu <[email protected]>
Signed-off-by: Xiangce Liu <[email protected]>
Signed-off-by: Xiangce Liu <[email protected]>
Signed-off-by: Xiangce Liu <[email protected]>
xiangce
added a commit
that referenced
this pull request
Mar 11, 2025
- Add IPv6 obfuscation, and generate relevant reports. IPv6 Obfuscation should keep the length of the original address after obfuscating. One IPv6 address, no matter compressed or exploded will be treat as one same address, hence has the same obfuscated result. - IPv6 obfuscation will be enabled individually by setting "obfuscate_ipv6=True" in insights-client.conf. And can be disabled for particular specs by adding "no_obfuscate=['ipv6']" in spec RegistryPoint - RHINENG-14804 Signed-off-by: Xiangce Liu <[email protected]>
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 IPv6 obfuscation, and generate relevant reports.
IPv6 Obfuscation should keep the length of the original address
after obfuscating.
One IPv6 address, no matter compressed or exploded will be
treat as one same address, hence has the same obfuscated
result.
IPv6 obfuscation will be enabled individually by setting
"obfuscate_ipv6=True" in insights-client.conf. And can
be disabled for particular specs by adding
"no_obfuscate=['ipv6']" in spec RegistryPoint
RHINENG-14804
All Pull Requests:
Check all that apply:
Complete Description of Additions/Changes:
Add your description here