Re:Chrome extensions are tampering with security headers
by sneak on Tuesday May 25, 2021 @09:10PM
(#27284914)
You forgot Cookie Autodelete, NoScript, and HTTPS Everywhere.
[ Parent
| on HN ]
Re:Chrome extensions are tampering with security headers
by cortesoft on Tuesday May 25, 2021 @09:15PM
(#27284957)
I think the fact that people are listing different sets of extensions they trust is good evidence that you can't just say "this list is the only list of extensions you can trust"
Re:Chrome extensions are tampering with security headers
by lmkg on Tuesday May 25, 2021 @09:31PM
(#27285073)
Frankly this is why I prefer a "maximalist" browser like Vivaldi (and old-school Opera) that focuses on building features into the core browser rather than supporting extensions. There are benefits to having a feature be provided directly by the browser, not the least of which is the trust model. There's a trade-off of fewer features overall and less customization, but it's a trade-off I'm personally fine with.
Re:Chrome extensions are tampering with security headers
by josefx on Wednesday May 26, 2021 @01:12AM
(#27286635)
Different people use different extensions. I have seen quite a few people avoid NoScript, not because they don't trust it, but because they considered manually selecting which scripts could run not worth their time.
Re:Chrome extensions are tampering with security headers
by sneak on Tuesday May 25, 2021 @11:11PM
(#27285777)
Outside of a small list of security extensions numbering a dozen or fewer, you can't really trust much of anything in the extension webstore.