Skip to content
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

Disable creation of wrapper for single binary #5241

Closed
WhyNotHugo opened this issue Jul 7, 2022 · 3 comments
Closed

Disable creation of wrapper for single binary #5241

WhyNotHugo opened this issue Jul 7, 2022 · 3 comments
Labels
duplicate This issue or pull request already exists firecfg Anything related to firecfg and not firejail itself

Comments

@WhyNotHugo
Copy link
Contributor

Is your feature request related to a problem? Please describe.

I have a system hook that runs firecfg each time a file is installed into /usr/bin.

However, this re-creates some link in /usr/local/bin that I don't want because sandboxing those applications is problematic.

I do want the links for most binaries, but I want a few exceptions.

Describe the solution you'd like

Some form of configuration file where I can specify names to skip when running firecfg.

Describe alternatives you've considered

Deleting the profiles should be possible, but since those are provided by firejail, they'll get reinstalled on update. I'm not a fan of altering / deleting package-provided files anyway.

It should be possible to instruct the package manager to ignore installing unwanted profiles, but that's not very portable and sounds like a big hack.

Additional context

I mostly want to disable to link in /usr/local/bin/ for some programs where the sandbox does not work well for me or still needs to be refined more.

@reinerh
Copy link
Collaborator

reinerh commented Jul 7, 2022

firecfg is only creating symlinks for programs/profiles that are mentioned in /etc/firejail/firecfg.config. Does this solve your problem?

@WhyNotHugo
Copy link
Contributor Author

Kinda... but not really.

I don't like the idea of mutating files provided by system packages (firejail in this case). It makes maintenance and setting up new hosts a bit tricky. For example, the file cannot be provided by a configuration meta-package because the file conflicts (owned by both).

Are you open to discussing more flexible solutions?

One possible approach is putting the file in /usr/share/factory/etc/firejail/firecfg.config and installing it via tmpfiles.d. So if the file is absent, it gets copied to /etc/firejail/firecfg.config at startup, but otherwise is left alone.

Another possible approach is to have a /etc/firejail/firecfg.d/ and place drop-in files in there which can exclude provides (via !mpv, for example).

@rusty-snake rusty-snake added duplicate This issue or pull request already exists firecfg Anything related to firecfg and not firejail itself labels Jul 7, 2022
@rusty-snake
Copy link
Collaborator

Duplicate of #2097

@rusty-snake rusty-snake marked this as a duplicate of #2097 Jul 7, 2022
@rusty-snake rusty-snake closed this as not planned Won't fix, can't repro, duplicate, stale Jul 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate This issue or pull request already exists firecfg Anything related to firecfg and not firejail itself
Projects
None yet
Development

No branches or pull requests

3 participants