Can I programmatically obtain the .crx of my published extension if I never had the key.pem?

[Z Yin]

I published an extension to CWS without creating key.pem first.

Then I find myself needing to provide .crx for some of my users who can't access CWS, and I want to make sure it has the same id as the CWS version.

Currently what I do is download the .crx from my CWS dashboard, but the problem is I can't automate it as part of building / releasing new patches.

Is there a way to build the .crx locally without having a .pem key? Or, is it possible to download the .crx from CWS in an automated way?

[Deco]

In order to do this you will need to maintain 2 separate redistributions of your extension locally. It is not possible to fetch the key from the CWS every time, instead what you will need to do is package the CRX on the browser itself from an unbundled state using the PEM key you download from CWS, then distribute this packaged CRX to those who require it separately.

Thanks,

Decklin 

--
You received this message because you are subscribed to the Google Groups "Chromium Extensions" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-extens...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/73d4db00-8148-4450-831d-a0ea02d739fen%40chromium.org.

[Z Yin]

>  using the PEM key you download from CWS

How can I download the pem key from CWS? I believed it was impossible.

[Deco]

Apologies there has been a miscommunication on my part, what I was meaning to infer is that in order to separate this function for the separate CRX branch you cannot use the CWS, it has to be maintained and updated locally.

How you will do this is by packaging the unbundled extension file structure that currently exists which will output the PEM key. You can then use this for sideloading updates onto the browser with this key - note however, this cannot be downloaded from the CWS, it must be maintained separately.

Thanks,

Decklin 

[Z Yin]

Hi, as I mentioned, I need to provide direct .crx download for some users, but want to ensure their extension ID is the same as the CWS ID. I'm confused about will your suggestion create a different ID? For instance, if I use the "Pack extension" button, it'll definitely generate a different ID.

[Deco]

What you are attempting to do is impossible, the suggestion I have given will indeed generate a new ID, it is the only realistic option for serving users who require a separate CRX however.

[Z Yin]

Well, it's not impossible if I had known better and created the pem key before the initial publishing, and then submit the pem key to CWS for the initial publishing.

[hrg...@gmail.com]

My understanding was that it's no longer possible to install .crx files locally. That functionality was removed from Chrome several years ago.

So, how are your users using the .crx file?

[Cuyler Stuwe]

My guess is that maybe at least one Chromium-based browser still allows you to install via CRX. 

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/b87f264d-3564-4092-b65e-d38ed4cd6258n%40chromium.org.

[Cuyler Stuwe]

For example, this page for Edge comes with a set of instructions for sideloading directly from CRX files on Mac/Linux:

https://docs.microsoft.com/en-us/microsoft-edge/extensions-chromium/developer-guide/alternate-distribution-options

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/CA%2BYuxdfJ_A%3DYxq8u%3DNWEaYOUCVoPu8BpXgHuXZ9ztaniLtrcbw%40mail.gmail.com.

[Cuyler Stuwe]

Chrome’s docs also still say you can sideload CRX on Linux (presumably because the “Linux market” is assumed to be intelligent/informed enough to be trusted to decide for themselves what software seems trustworthy?):

https://developer.chrome.com/docs/extensions/mv3/external_extensions/

[hrg...@gmail.com]

Well, in that case you can download your .crx file programmatically from this URL:

https://clients2.google.com/service/update2/crx?acceptformat=crx3&prodversion=200&response=redirect&x=uc%26id%3Daaaaabbbbbcccccdddddeeeeefffff

The last part in red must be your extension ID.

[Z Yin]

>  Well, in that case you can download your .crx file programmatically from this URL:

Thanks!!! This is the correct answer!