Ongoing interfaces work

[Zygmunt Krynicki]

On Thu, May 12, 2016 at 3:48 AM, Pedro Coca <pedro.coca at canonical.com> wrote:
>
>
> On Mon, May 9, 2016 at 2:47 PM, Daniel Holbach
> <daniel.holbach at canonical.com> wrote:
>>
>> Hello everybody,
>>
>> one of my action items from Ubuntu Online Summit was to start this
>> discussion to find out who's doing which work on interfaces right now.
>> Our idea was that it'd help if we brought engineers, testers, app
>> developers and others together early on and link to the various
>> available code branches from the documentation as examples.
>>
>> If you're involved in interfaces work, please speak up.
>
>
> After watching the UOS session regarding interfaces, one of the things that
> I would like to know is how could the 15.04 security overrides be
> implemented with interfaces. Would be great to know how the process of
> defining a new kind of interface works, if there is any input format and if
> the aforementioned case is a valid one. Would be enough to include the
> "snapd-interfaces"[1] on a LP bug like was mentioned on the UOS?

Yes, please use this tag to discuss all interface issues and topics.
Early next week we'll come up with draft document for the process of
getting a new interface in place.

> The particular case would be to see how to use interfaces for a streamer
> that uses a web camera feed with ffmpeg; With 15.04 we used the security
> override feature (apparmor for the USB camera access & seccomp for the
> set_priority call) to overcome these issues. Would there be any difference
> for a general case trying to use other syscalls not allowed by seccomp?

This is not so much about security as it is about interop and being
able to replace part on both end of the interface with compatible
elements and still have them work.

Having said that the override bits from 15.04 are a perfectly fine
starting point for creating a new interface.

Best regards
ZK