You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 wrong sha1 value.
actual sha1 value (40 digits)
765c4366dc2ac43e4f2b1b8525160f5c9c08b26e
crxviewer sha1 value (39 digits)
765c4366dc2ac43e4f2b1b852516f5c9c08b26e
Obviously, one character 0 is missing. I am curious why it is missing a character, I have also tested, other file Hash are fine, only sha1 has a problem with the hash type.
- 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.
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: