Thanks for working on this!
I noticed that this patch is not listed in the copyright file, it would
be great if someone could include the header from the ungoogled-chromium
repository.
On Wed, 26 Jul 2023 16:12:13 -0400 Andres Salomon
wrote:
> As Matt mentioned, this is something that we need to decide if we
want
> disabled at build time (deleting base_feature_status from
> third_party/blink/renderer/platform/runtime_enabled_features.json5 ,
> which would turn it back into a
In my opinion, as a maintainer and user of Chromium (as distinct from Chrome),
we absolutely need to ship this with the code removed / disabled. This is a
deliberate attempt to lock out the open Web, to force the use of a
Google-approved (and Google-locked) software, firmware, and hardware
As Matt mentioned, this is something that we need to decide if we want
disabled at build time (deleting base_feature_status from
third_party/blink/renderer/platform/runtime_enabled_features.json5 ,
which would turn it back into a blink field-trial option that's
disabled by default), disabled
Package: chromium
Version: 115.0.5790.102-2
Engineers working for Google have proposed a standard named
Web Environment Integrity
details available at
https://github.com/RupertBenWiser/Web-Environment-Integrity/blob/main/explainer.md
There have been hundreds of articles, social media
5 matches
Mail list logo
