mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #407] Created firejail ansible playbook #294
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#294
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 @ghost on GitHub (Apr 3, 2016).
Original GitHub issue: https://github.com/netblue30/firejail/issues/407
This playbook https://bitbucket.org/aaaaaaaaaaaaaaaaaaaaa1/ansible-firejail/overview will install firejail automatically on an ansible managed system. It could be improved by being yum/apt neutral.
It would be interesting to extend it such that it uses ansible's fact gathering mode to store a record of binaries syscall functions and use the stored facts to generate firejail profiles but that is more involved than what I have time for, hopefully someone else can take this up as a fun project!
Another advanced usage would be to use this for the basis of performing QA on firejail profiles on lists of programs that it is desired to jail. This can be achieved by using the result and register variables in ansible.
@netblue30 commented on GitHub (Apr 3, 2016):
Thanks, I put a link to it on the main project site: https://firejail.wordpress.com/