Sandboxing Plugins

[Martin Gräßlin]

On Thursday 04 April 2013 11:19:42 Marco Martin wrote:
> On Thursday 04 April 2013, David Baron wrote:
> > Known that a misbehaving plugin can crash plasma and our valient devs
> > cannot be responsibility for all the contributed code floating around.
> > 
> > Browsers have this same problem and Chromium solves it by running each
> > plugin as its own process. If it craches, everything else is still  up and
> > can play fine.
> > 
> > Possibility the a future plasma-desktop version could adopt this approach?
> 
> no.
> this is one of those things that has been discussed a lot in the past.
suggestion: at the sprint we write the arguments down in the wiki so that we 
have something to point to if the future comes up again. I'm fine with doing 
that as I consider the Chrome approach as extremely stupid.

--
Martin Gräßlin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/plasma-devel/attachments/20130404/a9ab3e39/attachment.sig>