-
Notifications
You must be signed in to change notification settings - Fork 120
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
Project full of JWT keys (hexadecimal) #775
Comments
Could it be a simple |
I'm not noticing any hexadecimal values in that code. I do see
which I'm assuming is some kind of base64 encoded value. We do support base64 but only when it has padding. Some related issues
Those have a mixture of symptoms and potential solutions in them. I'd recommend checking them out in case some of the discussion would be relevant for your case depending on what type of content you are dealing with and how it can be detected. One thing that is implemented today is the ability to define a regex to describe patterns that |
Thank you!
|
Putting those braces into brackets tricks TOML ❕ [default]
extend-ignore-re = ["'[{]\"id\":\".+[}]'"] |
|
You could take advantage of multi-line string literals: https://toml.io/en/v1.0.0#string |
[default]
extend-ignore-re = [
"'\\{\"id\":\".+\\}'",
"'\\[\\{\".+\"\\}\\]'"
] |
There are projects full of hexadecimal strings.
For example https://github.com/web-auth/webauthn-framework/blob/69c7a1635750a15c7b32891f0d123fb5fccacf74/tests/library/Unit/AttestationStatement/AndroidKeyAttestationStatementSupportTest.php#L91
Related to #32
How to deal with them?
I hope I should not exclude all files with hexadecimal strings :)
The text was updated successfully, but these errors were encountered: