mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #683] dns issue with network manager #468
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#468
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 @xahare on GitHub (Aug 4, 2016).
Original GitHub issue: https://github.com/netblue30/firejail/issues/683
when using --net on an internal address natted out, with a hosts that uses network manager, 127.0.1.1 is not available, so you have to use --dns. i dont know a good solution to this. ive tried
the other option is just use hosts main interface. these days which interface doesnt change. but, the address will, so a long running browser would still need to be restarted.
@netblue30 commented on GitHub (Aug 5, 2016):
You are right, there isn't any easy fix for it. The dns proxy on 127.0.1.1 will remain in the old network namespace, and it will not be available in the new namespace. What could work is another proxy to move data between loopback interface in the main network namespace and the loopback interface in the new network namespace. However, adding such a proxy will create some other security problems. The best solution is to find an external dns server you can trust, and this is difficult.
@xahare commented on GitHub (Aug 5, 2016):
how about overlay /etc/resolv.conf? you could have it listen for network changes or just check periodically.
was also thinking of making a container with unbound or dnsmasq "upstreaming" to localhost, but thats only slightly safer, attack surface wise, than running dnsmasq on the host.
@netblue30 commented on GitHub (Aug 7, 2016):
You are complicating yourself. Your router (DSL, cablemodem etc.) will give you the DNS settings it got from your ISP. More likely your ISP will forward your requests to some bigger ISP like Level 3 Communication, or whoever connects your ISP upstream. Can you trust any of this guys? Probably all of them are logging the requests. There is also the case when the home router is hacked and your bank http traffic is redirected to some fake bank website.
I would say find a dns server and put the IP address directly with "firejail --dns=... firefox"
@xahare commented on GitHub (Aug 8, 2016):
i was also looking for seamless transitions to places like work where you want the local nameservers. but those are not that common so its not that bad to restart the browser with a different script.