Disable Vulnerable Plugins

[anon71742606]

@invisnet

They may have other security measures in place that we don’t and can’t know about that would mitigate the problem.

At that point you’ve just broken a site for no good reason, and potentially lost them a lot of business. That doesn’t seem like a good idea.

@invisnet

I never suggested that we have any sort of remote access to sites - I can’t imagine anything worse than trying to secure that; only a Politician would think it’s a good idea.

That said, it doesn’t mean the CP install itself can’t disable a plugin if it’s suitably flagged by the plugin directory, and that could be configurable.

I’m still in 2 minds about whether it’s a good idea.

@james

Sounds like a good thing to put on our security screen as an option that is disabled by default.

@invisnet

It all gets very complex once you start adding settings for automatically disabling plugins. People will have different overall preferences, some plugins can be safely disabled on some sites but not others, some people will only want to disable some plugins for unauthenticated remote exploits, etc etc etc.

I don’t think the default setting as being “off” was ever in question, guys.
Nor do I think either of these gentlemen (or the others involved in these efforts) would override an explicit user preference / instruction.
And, for the record, I agree that I want to have the final choice as to what happens, or does not happen, on sites I control. Obviously others should have that same right.

So, as much as a preference for control over your site is perfectly valid, it does not address the core problem in this particular thread.

Which comes down to:

1. What can and what should the repository do in the case that plugin vulnerabilities are reported, but left un-patched?
   We have all seen what .org does, or rather does not do, and I think we would agree that such a solution leaves something to be desired.
2. If the user is given the option of disabling these plugins (which some users may choose to do and one should respect their preferences and autonomy as well), how can this be done safely?

Edit: Also, how is it possible to make sure that plugins with SUCH serious vulnerabilities that they require urgent heroic measures do not make it into the directory in the first place?