[GH-ISSUE #2274] Allowing the execution of a file? #1520

Open
opened 2026-05-05 08:10:56 -06:00 by gitea-mirror · 5 comments
Owner

Originally created by @ghost on GitHub (Nov 24, 2018).
Original GitHub issue: https://github.com/netblue30/firejail/issues/2274

How can I make firejail allow gimp to execute a single plugin?

In gimp.profile it says "noexec ${HOME}", but that disables execution of everything (as intended). How can prevent execution of anything on my /home folder EXCEPT in a folder like "/home/amarildo/.gimp-2.8/plug-ins/"?

Thanks

Originally created by @ghost on GitHub (Nov 24, 2018). Original GitHub issue: https://github.com/netblue30/firejail/issues/2274 How can I make firejail allow gimp to execute a single plugin? In gimp.profile it says "noexec ${HOME}", but that disables execution of everything (as intended). How can prevent execution of anything on my /home folder EXCEPT in a folder like "/home/amarildo/.gimp-2.8/plug-ins/"? Thanks
gitea-mirror added the
information_old
label 2026-05-05 08:10:56 -06:00
Author
Owner

@Vincent43 commented on GitHub (Nov 24, 2018):

Whitelisting specific dirs from noexec in not possible.

<!-- gh-comment-id:441393130 --> @Vincent43 commented on GitHub (Nov 24, 2018): Whitelisting specific dirs from `noexec` in not possible.
Author
Owner

@ghost commented on GitHub (Nov 24, 2018):

@amarildojr The current https://github.com/netblue30/firejail/blob/master/etc/gimp.profile doesn't enable noexec ${HOME} by default. If you're able to put your plugin in a system-wide location (defaults to /usr/lib/gimp/2.0/plug-ins, but any other path outside your $HOME set via gimp's preferences will do) you can enable noexec ${HOME} by adding it to /etc/firejail/gimp.local (which you need to create). This way you would have the best of both worlds: safeguarding your $HOME dir via noexec and using gimp plugins as you wish...

<!-- gh-comment-id:441395676 --> @ghost commented on GitHub (Nov 24, 2018): @amarildojr The current https://github.com/netblue30/firejail/blob/master/etc/gimp.profile doesn't enable `noexec ${HOME}` by default. If you're able to put your plugin in a system-wide location (defaults to /usr/lib/gimp/2.0/plug-ins, but any other path outside your $HOME set via gimp's preferences will do) you can enable `noexec ${HOME}` by adding it to /etc/firejail/gimp.local (which you need to create). This way you would have the best of both worlds: safeguarding your $HOME dir via noexec and using gimp plugins as you wish...
Author
Owner

@chiraag-nataraj commented on GitHub (Dec 9, 2018):

@amarildojr Maybe the bug/intended behavior in #2029 might help?

<!-- gh-comment-id:445541681 --> @chiraag-nataraj commented on GitHub (Dec 9, 2018): @amarildojr Maybe the bug/intended behavior in #2029 might help?
Author
Owner

@chiraag-nataraj commented on GitHub (May 20, 2019):

@amarildojr Is the above a satisfactory workaround? If so, I'll close this. I can also convert this to an enhancement request to allow file-specific whitelisting if that's better.

<!-- gh-comment-id:494026534 --> @chiraag-nataraj commented on GitHub (May 20, 2019): @amarildojr Is the above a satisfactory workaround? If so, I'll close this. I can also convert this to an enhancement request to allow file-specific whitelisting if that's better.
Author
Owner

@rusty-snake commented on GitHub (Apr 1, 2020):

should we close or add enhancement?

<!-- gh-comment-id:607337463 --> @rusty-snake commented on GitHub (Apr 1, 2020): should we close or add enhancement?
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/firejail#1520
No description provided.