Newbie question: Device permisssions

[Alec Leamas]

Hi Alberto,

On 01/07/18 19:15, Alberto Ruiz wrote:
>     On 01/07/18 14:43, Ryan Gonzalez wrote:
> 
>     > On July 1, 2018 3:07:51 AM Alec Leamas <leamas.alec at gmail.com
>     <mailto: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.
>     >>
>     >> 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.
> 


> 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?

Well, first part of process is certainly to not top-post... lists have a
habit of reading messages from top to bottom.

That said, I'm a newbie, but I'd assume that you could just file an
issue and possibly a PR to the flatpak github repo.

Cheers!
--alec