Andrey Rahmatullin writes ("Re: sane chromium default flags - include
--enable-remote-extensions"):
> On Mon, Feb 27, 2017 at 03:14:08PM +0000, Ian Jackson wrote:
> > Do we know why this is ? Is this an unintended side effect of some
> > other change ? Has someone done this deliberately and if so have they
> > explained what they were trying to achieve ?
> >
> > I can see that the behaviour you describe would be very annoying.
>
> When updating extensions is disabled, it is a "good" thing that you cannot
> install them and use installed ones.
> That's what the original bug was about.
I'm not sure I have parsed your reply correctly, so let me repeat back
what I think you are saying:
Since online updates to non-Debian-packaged extensions are disabled,
it is necessary to prevent installation or use of
non-Debian-packaged extensions at all: otherwise, users would be
running extensions without security updates.
Well, the reasoning is sound, but this does not seem like a desirable
situation.
Can we not make the updates work for non-Debian-packaged extensions,
while disabling them for Debian-packaged ones ?
If we did that then there would no need to disable people's
extensions.
(Of course a user should not be invited to install extensions from an
upstream or third-party extension repository, unless that repository
contains only free software, or the user has enabled Debian contrib -
but I think that's a separate question.)
Ian.
--
Ian Jackson <ijack...@chiark.greenend.org.uk> These opinions are my own.
If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.
