The credential provider is built for both chromium and Google Chrome branded builds. The former is useful so that unit tests will run on the chromium waterfall. However, this has other side effects:
- both chromium branded and Google Chrome branded builds use the same CLSIDs for registered COM objects. They should use different values.
- the chromium branded builds touches registry values under SOFTWARE\Google when it should SOFTWARE\Chromium
- the chromium branded builds should not touches registry values under SOFTWARE\Google\Update
Comment 1 by rogerta@chromium.org
, Oct 5