Intent to implement: New policy on external binary components

[Dominic Battre]

Hi.

We would like to propose a new policy about how we handle external binary components [1] in Chromium (the browser you build from the open source repository) so that the code can be easily verified, audited and customized.

This is the proposal:

https://docs.google.com/document/d/1JVkUot5hCy9J2EuYPY4gZz1uTt7y2EyrADzQ6NSyYdA/edit#

tl;dr: Chromium should not download binary components at runtime unless you tell it to do that via compile time flags.

We propose to set up this policy for new components and will see what we can do for existing code. (No promised timeline, yet.)

Your feedback would be appreciated.

Best regards,

Dominic, Balazs, Pawel and Peter

[1] see the linked document for a definition

-- 

Google Germany GmbH - Dienerstr. 12 - 80331 München - Germany

Registergericht und -nummer: Hamburg, HRB 86891
Sitz der Gesellschaft: Hamburg
Geschäftsführer: Graham Law, Christine Elizabeth Flores