Newbie question: Device permisssions

[Alberto Ruiz]

It seems to me this is something worth a portal, for apps like the Arduino
IDE and other apps that need to talk to the serial port. Whats the process
to propose and submit an implementation?

El dom., 1 jul. 2018 14:06, Alec Leamas <leamas.alec at gmail.com> escribió:

>
>
> On 01/07/18 14:43, Ryan Gonzalez wrote:
>
> > On July 1, 2018 3:07:51 AM Alec Leamas <leamas.alec at gmail.com> wrote:
>
> >> I'm trying to package opencpn, a navigation program requiring access to
> >> serial data, typically on a device like /dev/ttyS0 or /dev/ttyUSB0.
> >>
> >> In traditional rpm packaging, access to these devices is handled using
> >> the group permissions. The devices are typically 660 and owned by
> >> root:dialout. Adding dialout to the running user's secondary groups
> >> gives her r/w access to the device without too much fuzz.
> >>
> >> Howwever, my too small brain cannot understand how to handle this is in
> >> a flatpak package. The device ownership in the sandbox is
> >> nfsnobody:nfsnobody, so the sandbox user cannot access it, permissions
> >> being 660.
> >>
> >> The brute force method would be to add a udev rule changing permissions
> >> and/or ownership of the device. But, before making this somewhat drastic
> >> step: Is there any other way to give the sandbox user r/w permissions to
> >> the devices involved?
>
> > Try passing --device=all in finish-args:
> > http://docs.flatpak.org/en/latest/sandbox-permissions.html#device-access
>
>
> yes.. already done that. The devices are visible, but unusable due to
> the nfsnobody:nfsnobody ownership and 660 permissions in the sandbox.
>
> Cheers!
>
> --alec
> _______________________________________________
> Flatpak mailing list
> Flatpak at lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/flatpak
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/flatpak/attachments/20180701/c03d7d14/attachment.html>