mmadfox/go-crx3

Chrome browser extension tools. Provides a set of tools packing, unpacking, zip, unzip, download, etc.

go-crx3's Issues

File name interception problem after decompression

After I decompress the file name will be intercepted more。
Originally from golang strings.TrimRight()

println(strings.TrimRight("CaptainBIapp.zip", ".zip")) //CaptainBIa

Because I need the unzipped file name, but the api return value is not provided. The file name was intercepted in the previous step, which caused the file name to not match, and the file could not be read.

Extend `keygen` command to support RSA-3072 and RSA-4096

Right now in crx3 new private keys are hardcoded to be RSA-2048. I haven't investigated current support for RSA-3072 and RSA-4096 in CRX in Google Chrome (or Microsoft Edge), but at least per CRX₃ Design Doc they intended to use bigger keys, RSA-4096 specifically, so it would be good to support them (and ideally switch to at least RSA-3072 by default).

Extracting key from crx without installing to chrome

I have a crx3 and would like to extract the key from the crx without installing it into chrome.
But I didn't find a counterpart, so I hope a little hint will help, thanks!

Installed and got "crx3: command not found"

go install github.com/mediabuyerbot/go-crx3/crx3@latest
go: downloading github.com/mediabuyerbot/go-crx3 v1.4.0
go: downloading github.com/spf13/cobra v1.3.0
go: downloading google.golang.org/protobuf v1.28.1

crx3 download https://chrome.google.com/webstore/detail/amazon-tag-remover/mmajdhfdokfcaiadahjnffhbfjfkmcnc`
-bash: crx3: command not found

go list crx3
package crx3 is not in GOROOT (/usr/local/Cellar/go/1.20.1/libexec/src/crx3)

Support `key` command

id command is already supported, but another useful one would be key.

key should be equivalent of what following command does on private key:
openssl rsa -in key.pem -pubout -outform DER | openssl base64 -A

If CRX/ZIP's manifest.json has a key field, then key command could be made to work also on such CRX/ZIP files and display their key then.

This key value is useful for developers to keep consistent ID:
https://developer.chrome.com/docs/extensions/reference/manifest/key

---

BTW thank you for creating the tool! This year I have to update my web browser extension, NavigUp, and migrate to Manifest V3 (known issues, checklist) to ensure its users won't be impacted by Manifest V2 support timeline, specifically:

June 2024: Chrome MV2 deprecation pre-stable rollout
June 2024 + 1-X months: Chrome MV2 deprecation stable rollout

At some point Chrome deprecated CRX2 format and introduced CRX3 - CRX₃ Design Doc. Beside relying on Chrome Web Store, I always self-hosted my extension too, so being able to create CRX3 easily will be super handy.

---

In the distant past I used crxmake, possibly https://github.com/Constellation/crxmake, but I have no notes to tell for sure. I refuse to accept need to use hundred megabyte browser binary to create crx file. If not for your tool, i.e. crx3, I would possibly had to write one for myself (most likely in C/C++). There are some JavaScript based solutions, but I'm not fan of JavaScript runtime environments like Node.js, and prefer more standalone solutions.