[Pkg-chromium-maint] Bug#856183: What's a safe way to have extensions in chromium in Debian?

Sebastian Reichel sre at debian.org
Thu Mar 23 06:50:13 UTC 2017


On Wed, Mar 22, 2017 at 12:03:02PM +0100, Enrico Zini wrote:
> now we have extensions disabled in Chromium by default. If I did my
> homeworks correctly, that prevents Chromium from phoning home by
> default, and prevents a previous scenario where extensions could be
> installed but not upgraded, becoming security issues over time.
> Now, suppose I need an extension, what is the proper way to have it in
> Debian, so that it gets upgraded when needed? With that proper way, what
> amount of phoning home is going to happen?
> Since this looks like it's going to be a major issue with stretch, can I
> have some authoritative wiki page / FAQ entry that tells me how I can
> deal with it cleanly, and that I can easily send to confused people?

I wonder if we could just add a boolean debconf question for this.
It could setup /etc/chromium.d/remote-extensions based on the answer
and provide some (dis)advantages info for selecting either option.

-- Sebastian
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-chromium-maint/attachments/20170323/4375533d/attachment.sig>

More information about the Pkg-chromium-maint mailing list