Hi, I would think that the security concerns can be minimized, if not completely eliminated, by setting up a way to have one snap application invoke another, possibly itself. In theory, a snap itself is already vetted and running in a secure environment. So what's insecure about one snap asking the system to invoke another? Perhaps there are some constraints on that which need to be had as well. In any case, my snap might call some other snap that Ubuntu publishes (that is endowed with special privileges) that is delegated the responsibility of invoking processes outside the secure environment, such as a browser.
I don't know; I'm just brain-storming. Obviously I don't know enough about the snap technology to talk about it intelligently. I still need to get a grip on the plugs and slots. On Thu, Oct 20, 2016 at 1:00 AM, Mark Shuttleworth <[email protected]> wrote: > > This is an active discussion for us at the moment, I think we will have > a solution for you soon. > > Mark > > -- > Snapcraft mailing list > [email protected] > Modify settings or unsubscribe at: https://lists.ubuntu.com/ > mailman/listinfo/snapcraft >
-- Snapcraft mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/snapcraft
