mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #1085] option to expose only whitelisted ip:port:protocol into the sandbox #739
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#739
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 @ibukanov on GitHub (Jan 31, 2017).
Original GitHub issue: https://github.com/netblue30/firejail/issues/1085
To restrict the sandbox networking it is nice to allow for the sandbox to reach only single ip:port:protocol outside the sandbox. My use case is to expose http proxy running on my laptop into the sandbox so the only connection to the outside world is through this proxy.
Currently it is possible with --netns and custom iptable rules, but that requires root.
@netblue30 commented on GitHub (Feb 1, 2017):
I would try a setup similar to this one: https://firejail.wordpress.com/documentation-2/basic-usage/#routed
Start a http proxy on 10.10.20.1
You also need a DNS proxy on 10.10.20.1. If you are running on Ubuntu, you already have one - it is probably listening only on 127.0.0.1, so you'll have to reconfigure it.
Start the sandbox: