ungoogled-chromium: Why cannot webstore detect ungoogled-chromium exactly?

So someone mentioned that UC cannot install extensions from webstore and I tried with vanilla UC on Windows and Arch and both of them can be recognized by webstore.

I searched through the issues here and all I can find is issues about drag&drop of crx files, like #1009, #988 and #923, but there is no explanation why exactly webstore cannot detect the browser. I have seen in this issue that it may have something to do with safe browsing, does this mean it is unfixable without enabling safe brwosing?

To put it simple, is it:

unsolvable? or
no one looked into this before? or
against the goal of the project so it is not fixed?

About this issue

Original URL
State: closed
Created 4 years ago
Comments: 50 (50 by maintainers)

Most upvoted comments

I haven’t found where cryptotoken is included though but that’s the best bet because I remember it is in the extension page for vanilla chromium.

A quick grep in chrome/browser (not likely to be in other directories due to Chromium architecture) shows that cryptotoken/manifest.json is referenced in chrome/browser/browser_resources.grd, which makes sense as all embedded resources must be referenced via .grd files (i.e. GRIT files). The GRIT name for this manifest.json is IDR_CRYPTOTOKEN_MANIFEST
Doing a grep for IDR_CRYPTOTOKEN_MANIFEST in chrome/browser hits two locations:

chrome/browser/extensions/component_loader.cc in ComponentLoader::AddDefaultComponentExtensionsWithBackgroundPages(). This seems like where all the actual component extension loading is being done (at least one of them; there’s another for kiosk mode).
chrome/browser/extensions/component_extensions_whitelist/whitelist.cc in function IsComponentExtensionWhitelisted. This function is referenced in ComponentLoader::Add(), so it might be a security check to prevent unauthorized components.

Hopefully my thought process here helps.

Eloston on Jun 24, 2020

It’s been a while, but I believe this is because of patches/core/ungoogled-chromium/disable-webstore-urls.patch.

IIRC, the “Add to Chromium” button is provided by NeverDecaf’s chromium-webstore extension. In regular Chromium, it would be “Add to Chrome”.

Ideally we would re-enable detection in the Webstore, and use #285 to fix installations. I’d like to use #285 to re-enable extension installation because it allows us to not hardcode webstore URLs, and would enable users to install from non-Webstore sources (which is what NeverDecaf’s extension does when it self-updates).

Eloston on Jun 13, 2020

2020-06-08_18:32:15 I’d be commiting heresy, but works on my machine™

jstkdng on Jun 8, 2020