Skip to content
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

Identifies JWT as LTC/Ripple/BCH-Wallet-Adress #29

Open
tolik518 opened this issue Dec 13, 2022 · 1 comment
Open

Identifies JWT as LTC/Ripple/BCH-Wallet-Adress #29

tolik518 opened this issue Dec 13, 2022 · 1 comment

Comments

@tolik518
Copy link

Input: eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkpvaG4gRG9lIiwiaWF0IjoxNTE2MjM5MDIyfQ.SflKxwRJSMeKKF2QT4fwpMeJf36POk6yJV_adQssw5c

Output:
Found Possible Identifications :)

Matched text Identified as Description
eyJhbGciOiJIUzI1..._adQssw5c Litecoin (LTC) Wallet Address URL: https://live.blockcypher.com/ltc/address/eyJhbGciOiJIUzI1..._adQssw5c

Expected "Identified as" would be JWT.
Shortened the JWT for better visibility.


Another example:

Input: eyJhbGciOiJIUzI1NiJ9.eyJmb28iOiJiYXIifQ.JTvQIxZOL_-00JdKfTAEmhV-a6KUlB6OUWM8NuN7MN8
Output: No Possible Identifications :(

Expected "Identified as" would be JWT.

@swanandx
Copy link
Owner

It is due to regex crate not supporting look-around, as it is mentioned in release note .
We would need to rewrite the JWT regex without lookarounds.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants