pigmonkey / firewarden

Open a file via the specified application within a private Firejail sandbox.
The Unlicense
74 stars 7 forks source link

Does not work in Void linux ? #2

Closed ghost closed 7 years ago

ghost commented 7 years ago

Hi @pigmonkey ! This morning I noticed your package in AUR. It sounded interesting, so I decided to create a new package for Void linux, see here, but something is wrong when I run your script... I'm not very experienced in packaging, but I try to learn, so your help will be very appreciated! :wink:

Regards.

pigmonkey commented 7 years ago

Your link to the Void forums is timing out for me. Can you explain here what problem you're experiencing?

ghost commented 7 years ago

See this very short log for example.

"Warning: cannot find /var/run/utmp" => certainly because it's "/run/utmp" in Void.

Void linux is a little different from the other distros. For exemple Void uses glibc and musl, and musl is very strict regarding scripts & POSIX.

pigmonkey commented 7 years ago

So it looks like the script is executing Firejail successfully, which is all it is supposed to do, but then Firejail fails. Try launching viewnior like this:

$ /usr/bin/firejail --private-srv=firewarden/2017-06-04T11:17:09-07:00 --private-opt=firewarden/2017-06-04T11:17:09-07:00 --private viewnior

That is essentially what firewarden does when you call firewarden viewnior. I'm guessing it fails in the same way.

If that fails, try it without the --private-srv and --private-opt flags (which were just introduced in Firejail 0.9.46).

ghost commented 7 years ago

$ /usr/bin/firejail --private-srv=firewarden --private-opt=firewarden --private viewnior

This command fails, as in my first example, see the log.

Now, without the --private-srv and --private-opt flags:

$ /usr/bin/firejail --private viewnior

It seems to be working ! :smiley:

pigmonkey commented 7 years ago

Ok. You should report the issue with --private-srv and --private-opt on Firejail's issue tracker.

ghost commented 7 years ago

Thanks for the help, @pigmonkey

We could close this issue, then ?