github-starred/firejail

Fork 0

mirror of https://github.com/netblue30/firejail.git synced 2026-05-15 22:01:33 -06:00

[GH-ISSUE #1547] Too restrictive blacklisting for systemd-resolved, unable to browse the web due to broken resolv.conf symlink #1030

New issue

Closed

opened 2026-05-05 07:19:47 -06:00 by gitea-mirror · 4 comments

gitea-mirror commented

2026-05-05 07:19:47 -06:00

Owner

Originally created by @ThibaultMndr on GitHub (Sep 14, 2017).
Original GitHub issue: https://github.com/netblue30/firejail/issues/1547

With firejail 0.9.50 on Arch, disable-common.inc blacklists /var/run/systemd. But with a systemd-resolved configuration /etc/resolv.conf is a symlink to /var/run/systemd/resolve/resolv.conf, so the link is broken in jails.

Adding noblacklist /var/run/systemd before including /etc/firejail/disable-common.inc in profiles that require accessing internet is a workaround.

It should be more secure to only allow access to /var/run/systemd/resolve/resolv.conf but I don't know if it is possible without blacklisting individually all var/run/systemd subfolders

Originally created by @ThibaultMndr on GitHub (Sep 14, 2017). Original GitHub issue: https://github.com/netblue30/firejail/issues/1547 With firejail 0.9.50 on Arch, `disable-common.inc` blacklists `/var/run/systemd`. But with a systemd-resolved configuration `/etc/resolv.conf` is a symlink to `/var/run/systemd/resolve/resolv.conf`, so the link is broken in jails. Adding `noblacklist /var/run/systemd` before including `/etc/firejail/disable-common.inc` in profiles that require accessing internet is a workaround. It should be more secure to only allow access to `/var/run/systemd/resolve/resolv.conf` but I don't know if it is possible without blacklisting individually all `var/run/systemd` subfolders

gitea-mirror

2026-05-05 07:19:47 -06:00

closed this issue
added the
bug
label

gitea-mirror commented

2026-05-05 07:19:52 -06:00

Author

Owner

@netblue30 commented on GitHub (Sep 14, 2017):

I'll disable the blacklist in /etc/firejail/disable-common.inc, thanks for the bug.

@netblue30 commented on GitHub (Sep 14, 2017): I'll disable the blacklist in /etc/firejail/disable-common.inc, thanks for the bug.

gitea-mirror commented

2026-05-05 07:19:53 -06:00

Author

Owner

@netblue30 commented on GitHub (Sep 14, 2017):

Fixed: 1e879f1199

@netblue30 commented on GitHub (Sep 14, 2017): Fixed: https://github.com/netblue30/firejail/commit/1e879f1199fb3a3647a5eefd7a8f34bbdc8b8098

gitea-mirror commented

2026-05-05 07:19:54 -06:00

Author

Owner

@oxwivi commented on GitHub (Apr 23, 2018):

Does this issue still apply to the version shipping with Ubuntu 16.04 repo?

@oxwivi commented on GitHub (Apr 23, 2018): Does this issue still apply to the version shipping with Ubuntu 16.04 repo?

gitea-mirror commented

2026-05-05 07:19:56 -06:00

Author

Owner

@oxwivi commented on GitHub (Apr 23, 2018):

I compiled and installed, yes, issue still applies to the version shipping on Ubuntu repos. However, the firejail on repo version added a helpful [] indicator around the prompt to show currently in firejail'd env, compiled version doesn't. How do I activate it?

@oxwivi commented on GitHub (Apr 23, 2018): I compiled and installed, yes, issue still applies to the version shipping on Ubuntu repos. However, the `firejail` on repo version added a helpful `[]` indicator around the prompt to show currently in `firejail`'d env, compiled version doesn't. How do I activate it?

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/firejail#1030

No description provided.

Rows
Columns