-
Notifications
You must be signed in to change notification settings - Fork 569
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conflict with jailtest utility #4268
Comments
Is this tool actually needed globally? Personally I would answer 'yes'. Now that --audit is gone this tool is pretty nice to check running sandboxes.
firejailtest, firetest, jailcheck - just a few ideas (didn't check for any name collisions)... |
Thanks, I'll move it to "jailcheck". How do we check for collisions? |
@glitsj16 commented 2 days ago:
@netblue30 commented 3 hours ago:
On Arch, it can be done with with $ pacman -F firejail
community/firejail 0.9.64.4-1
usr/bin/firejail
usr/share/bash-completion/completions/firejail
$ pacman -F jailtest firejailtest firetest jailcheck I doesn't check the AUR though. And according to the Pacman Rosetta, on Debian this can be done with: apt-file search |
And for Fedora it is
|
Yes, that's correct. There is also no conflict in Debian:
|
jailcheck all set! |
The new
jailtest
utility conflicts with a utility of the same name included inuml-utilities
(Debian),uml_utilities
(Fedora, Arch AUR).They are installed in the same location (
/usr/bin/jailtest
). This means for packaging, that aBreaks
relationship needs to be declared, which means that firejail can not be co-installed with the uml-utilities package. This is very user-unfriendly and should be avoided if possible. As it has not been released yet, avoiding a conflict is still possible.Is this tool actually needed globally? Or would it be sufficient to have it in a private directory (like
/usr/lib/firejail/
, where other helper tools like fldd are located)?If the tool really is supposed to be invoked by users manually, could we think of a different name to avoid a conflict?
Alternatively I'm also considering not shipping it in the Debian package.
Any opinions?
Ping @netblue30
The text was updated successfully, but these errors were encountered: