mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #159] Bitlbee profile #110
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#110
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 @rogshdo on GitHub (Nov 26, 2015).
Original GitHub issue: https://github.com/netblue30/firejail/issues/159
I would like to create a profile for bitlbee so that I can run it in a jail. Currently I have this, built off of the server.profile and some of the other default profiles I see:
This seems to work, but I don't really understand
protocolornetfilter. Could someone more familiar with firejail suggest what a good profile should look like for bitlbee? Thank you!Also, if a bitlbee profile could be included with firejail by default, that would be great.
@netblue30 commented on GitHub (Nov 27, 2015):
I've just added your profile, thanks! This is how it looks:
You don't need "netfilter". This option works only if you create a network namespace, and BitlBee will probably not work in a network namespace.
"protocol unix,inet,inet6" describes the protocols allowed by socket system call. There are about 40 of them available, usually you can get away only with unix socket protocol, IPv4 and IPv6. The option is based on seccomp and reduces the attack surface of the kernel.
@rogshdo commented on GitHub (Nov 27, 2015):
Great, thanks!