mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #36] Support for symlink to firejail binary #16
Labels
No labels
LTS merge
LTS merge
bug
bug
converted-to-discussion
doc-todo
documentation
duplicate
enhancement
file-transfer
firecfg
firejail-in-firejail
firetools
graphics
help wanted
information_old
installation
invalid
modif
moved
needinfo
networking
notabug
notourbug
old-version
overlayfs
packaging
profile-request
pull-request
question
question_old
removal
runtime-permissions
sandbox-ipc
security
stale
wiki
wiki
wontfix
wordpress
workaround
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/firejail#16
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @blueyed on GitHub (Aug 20, 2015).
Original GitHub issue: https://github.com/netblue30/firejail/issues/36
It would be useful to support symlinks to the
firejailbinary, which means that a symlinkfirefoxtofirejailwould startfirefox, instead ofbash.The idea comes from envoy.
This would allow you to add a symlink
firefoxto e.g.~/bin, and it would automatically use firejail, if~/binis before/usr/binin your PATH.@ghost commented on GitHub (Aug 20, 2015):
This could work if it was restricted to a few known commands (like
firefoxorchrome) and then run them in--shell=nonemode to handle command-line arguments the same as normal.@netblue30 commented on GitHub (Aug 21, 2015):
That's a cool idea, thanks!
envoy people (https://github.com/vodik/envoy) are doing something very interesting in "Wrappers with envoy" section. It seems to me all we need is a simple bash script with the same name as the executable, and we put the bash script in the path before the original executable.
For example for transmission-gtk (bittorrent client), we add the script in /usr/local/bin directory:
In the script we need the full path (/usr/bin/transmission-gtk), otherwise we'll end up calling ourselves in a loop forever. It works today, it is integrated by default with the file manager, desktop menus and icons. You click on a torrent file and it automatically opens the bittorent client in a sandbox.