-
Notifications
You must be signed in to change notification settings - Fork 231
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
Huge Bug: sha-1
hash is missing one character
#104
Comments
Thanks for the report. This was due to an incorrect bound check; crxviewer/src/lib/modern-crypto.js Line 20 in e150056
|
JustOff
pushed a commit
to JustOff/esrc-explorer
that referenced
this issue
Feb 22, 2021
Rob--W
added a commit
that referenced
this issue
Mar 28, 2022
- Rely on CORS instead of work-arounds for public XPI files from AMO (#92) - Add work-around for crx access in Brave (#91) - Support source viewing of extensions from Microsoft Edge (#95) - Remove web_accessible_resourced to avoid UUID leak (#100) - Correct 0-padding of hashes (#104) - Update jsbeautifier to v1.14.0 (#110) - Support source viewing of extensions from Thunderbird (#111) - Fix domain front of AMO in Firefox add-on (#115) - Recognize CRX3 files served by addons.opera.com (#118) - Opera only: Add work-around to access addons.opera.com (#119) - web only: Add crx keyword to input field for keyword search (#99) - web only: Avoid breakage of web version when an extension runs a script (#113) - Refactor: remove unsupported declarativeWebRequest path - Refactor: Use declarative page actions to show button.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When I was comparing, kept prompting errors, and I was curious.After further comparing with the local hash tool, I found that the file itself was no problem.It was
crxviewer
that brought the wrongsha1
value.Obviously, one character
0
is missing. I am curious why it is missing a character, I have also tested, other fileHash
are fine, onlysha1
has a problem with the hash type.Specific steps:
extension (EXIF QuickView)
https://chrome.google.com/webstore/detail/kjihpkahhpobojbdnknpelpgmcihnepj
chrome-extension://jifpbeccnghkjeaalbbjmodiffmgedin/crxviewer.html?crx=kjihpkahhpobojbdnknpelpgmcihnepj
🔍
content\.js$
So, can you investigate and see if there are hidden dangers that cause sha-1 hash calculation errors?
The text was updated successfully, but these errors were encountered: