github-starred/firejail
2
0
Fork 0
mirror of https://github.com/netblue30/firejail.git synced 2026-05-15 14:16:14 -06:00
Code Issues 531 Projects Packages Wiki Activity Actions 6

[GH-ISSUE #698] Whitelisting /var is broken #476

New issue
Closed
opened 2026-05-05 05:56:03 -06:00 by gitea-mirror · 6 comments
gitea-mirror commented 2026-05-05 05:56:03 -06:00
Owner
Copy link

Originally created by @knoy on GitHub (Aug 11, 2016).
Original GitHub issue: https://github.com/netblue30/firejail/issues/698

Inserting the following into a profile:

blacklist /var
whitelist /var/log
whitelist /var/lib

Doesn't work and results in all of /var/lib and /var/log being unreadable.

Adding
--whitelist=/var/lib
as a command line argument makes all of /var visible

Originally created by @knoy on GitHub (Aug 11, 2016). Original GitHub issue: https://github.com/netblue30/firejail/issues/698 Inserting the following into a profile: > blacklist /var > whitelist /var/log > whitelist /var/lib Doesn't work and results in all of /var/lib and /var/log being unreadable. Adding ` --whitelist=/var/lib ` as a command line argument makes all of /var visible
gitea-mirror 2026-05-05 05:56:03 -06:00
gitea-mirror commented 2026-05-05 05:56:10 -06:00
Author
Owner
Copy link

@Fred-Barclay commented on GitHub (Aug 11, 2016):

G'day knoy! What version of firejail are you using?

As far as the profile goes, blacklist should override whitelist in this case, keeping all of /var/ unreadable. What you probably want to do is this
blacklist /var
noblacklist /var/log
noblacklist /var/lib

That will blacklist all of /var except for /var/lib/ and /var/log/.

This is what --whitelist=/var/lib does on my computer:
$ ls /var/
backups cache lib local lock log mail opt run spool state tmp

$ firejail --whitelist=/var/lib /bin/dash
Reading profile /etc/firejail/default.profile
Reading profile /etc/firejail/disable-common.inc
Reading profile /etc/firejail/disable-programs.inc
Reading profile /etc/firejail/disable-passwdmgr.inc

*\* Note: you can use --noprofile to disable default.profile **

Parent pid 15236, child pid 15237

Child process initialized
$ ls /var
lib

Hope this helps. :)
Fred

<!-- gh-comment-id:239233468 --> @Fred-Barclay commented on GitHub (Aug 11, 2016): G'day knoy! What version of firejail are you using? As far as the profile goes, `blacklist` should override `whitelist` in this case, keeping all of /var/ unreadable. What you probably want to do is this `blacklist /var` `noblacklist /var/log` `noblacklist /var/lib` That will blacklist all of /var except for /var/lib/ and /var/log/. This is what `--whitelist=/var/lib` does on my computer: `$ ls /var/` `backups cache lib local lock log mail opt run spool state tmp` `$ firejail --whitelist=/var/lib /bin/dash` `Reading profile /etc/firejail/default.profile` `Reading profile /etc/firejail/disable-common.inc` `Reading profile /etc/firejail/disable-programs.inc` `Reading profile /etc/firejail/disable-passwdmgr.inc` ` ` `*\* Note: you can use --noprofile to disable default.profile **` ` ` `Parent pid 15236, child pid 15237` ` ` `Child process initialized` `$ ls /var` `lib` Hope this helps. :) Fred
gitea-mirror commented 2026-05-05 05:56:14 -06:00
Author
Owner
Copy link

@knoy commented on GitHub (Aug 11, 2016):

I'm on debian using firejail version 0.9.40.

I've tried your 'noblacklist' approach but that doesn't work either:

[jails@jails ~]$ ls -la /var
ls: cannot open directory /var: Permission denied
[jails@jails ~]$ ls -la /var/lib
ls: cannot access /var/lib: Permission denied
[jails@jails ~]$ ls -la /var/log
ls: cannot access /var/log: Permission denied

If I remove the blacklist command in the profile, I can read the dirs no problem

<!-- gh-comment-id:239238421 --> @knoy commented on GitHub (Aug 11, 2016): I'm on debian using firejail version 0.9.40. I've tried your 'noblacklist' approach but that doesn't work either: ``` [jails@jails ~]$ ls -la /var ls: cannot open directory /var: Permission denied [jails@jails ~]$ ls -la /var/lib ls: cannot access /var/lib: Permission denied [jails@jails ~]$ ls -la /var/log ls: cannot access /var/log: Permission denied ``` If I remove the blacklist command in the profile, I can read the dirs no problem
gitea-mirror commented 2026-05-05 05:56:17 -06:00
Author
Owner
Copy link

@knoy commented on GitHub (Aug 11, 2016):

Even without blacklisting at all this is apparently broken for /var/log and /var/lib? Looks like firejail is doing some behind the scenes magic with /var .. specifically a344c555ff/src/firejail/fs_var.c (L110)

This looks like its overriding anything done. A bunch of hardcoded and undocumented paths seems a little messy way to go about this.

<!-- gh-comment-id:239238452 --> @knoy commented on GitHub (Aug 11, 2016): Even without blacklisting at all this is apparently broken for /var/log and /var/lib? Looks like firejail is doing some behind the scenes magic with /var .. specifically https://github.com/netblue30/firejail/blob/a344c555ff282c23a8274d10ad0f75eb4fae6836/src/firejail/fs_var.c#L110 This looks like its overriding anything done. A bunch of hardcoded and undocumented paths seems a little messy way to go about this.
gitea-mirror commented 2026-05-05 05:56:19 -06:00
Author
Owner
Copy link

@Fred-Barclay commented on GitHub (Aug 11, 2016):

Can you post the profile you are using?

<!-- gh-comment-id:239240952 --> @Fred-Barclay commented on GitHub (Aug 11, 2016): Can you post the profile you are using?
gitea-mirror commented 2026-05-05 05:56:20 -06:00
Author
Owner
Copy link

@netblue30 commented on GitHub (Aug 11, 2016):

Let's mark it as a bug, I'll take a look. Yes, Firejail mounts by default a new /var/log and modifies some directories in /var/lib.

<!-- gh-comment-id:239283425 --> @netblue30 commented on GitHub (Aug 11, 2016): Let's mark it as a bug, I'll take a look. Yes, Firejail mounts by default a new /var/log and modifies some directories in /var/lib.
gitea-mirror commented 2026-05-05 05:56:23 -06:00
Author
Owner
Copy link

@netblue30 commented on GitHub (Aug 12, 2016):

@Fred-Barclay is right:

As far as the profile goes, blacklist should override whitelist in this case, keeping all of /var/ unreadable.

By default firejail does a lot of filesystem cleanup before blacklisting and whitelisting. You can see all the steps if you run it with --debug:

$ firejail --debug
Command name #bash#
Attempting to find default.profile...
Found default profile in /etc/firejail directory
Reading profile /etc/firejail/default.profile
Reading profile /etc/firejail/disable-common.inc
Reading profile /etc/firejail/disable-programs.inc
Reading profile /etc/firejail/disable-passwdmgr.inc

** Note: you can use --noprofile to disable default.profile **

DISPLAY :0.0, 0
Using the local network stack
Parent pid 16412, child pid 16413
Initializing child process
Host network configured
PID namespace installed
Mounting tmpfs on /run/firejail/mnt directory
Mounting read-only /bin, /sbin, /lib, /lib32, /lib64, /usr, /etc, /var
Mounting tmpfs on /var/lock
Mounting tmpfs on /var/tmp
Mounting tmpfs on /var/log
Mounting tmpfs on /var/lib/dhcp
Mounting tmpfs on /var/lib/nginx
Mounting tmpfs on /var/lib/sudo
Mounting tmpfs on /var/cache/apache2
Create the new utmp file
Mount the new utmp file
Cleaning /home directory
Sanitizing /etc/passwd, UID_MIN 1000
Sanitizing /etc/group, GID_MIN 1000
Disable /home/netblue/.config/firejail
Disable /run/firejail/network
Disable /run/firejail/bandwidth
Disable /run/firejail/name
Disable /run/firejail/x11
Remounting /proc and /proc/sys filesystems
Remounting /sys directory
Disable /sys/firmware
Disable /sys/hypervisor
Disable /sys/fs
Disable /sys/module
Disable /sys/power
Disable /sys/kernel/debug
Disable /sys/kernel/vmcoreinfo
[...]

What exactly are you trying to do?

<!-- gh-comment-id:239462018 --> @netblue30 commented on GitHub (Aug 12, 2016): @Fred-Barclay is right: > As far as the profile goes, blacklist should override whitelist in this case, keeping all of /var/ unreadable. By default firejail does a lot of filesystem cleanup before blacklisting and whitelisting. You can see all the steps if you run it with --debug: ``` $ firejail --debug Command name #bash# Attempting to find default.profile... Found default profile in /etc/firejail directory Reading profile /etc/firejail/default.profile Reading profile /etc/firejail/disable-common.inc Reading profile /etc/firejail/disable-programs.inc Reading profile /etc/firejail/disable-passwdmgr.inc ** Note: you can use --noprofile to disable default.profile ** DISPLAY :0.0, 0 Using the local network stack Parent pid 16412, child pid 16413 Initializing child process Host network configured PID namespace installed Mounting tmpfs on /run/firejail/mnt directory Mounting read-only /bin, /sbin, /lib, /lib32, /lib64, /usr, /etc, /var Mounting tmpfs on /var/lock Mounting tmpfs on /var/tmp Mounting tmpfs on /var/log Mounting tmpfs on /var/lib/dhcp Mounting tmpfs on /var/lib/nginx Mounting tmpfs on /var/lib/sudo Mounting tmpfs on /var/cache/apache2 Create the new utmp file Mount the new utmp file Cleaning /home directory Sanitizing /etc/passwd, UID_MIN 1000 Sanitizing /etc/group, GID_MIN 1000 Disable /home/netblue/.config/firejail Disable /run/firejail/network Disable /run/firejail/bandwidth Disable /run/firejail/name Disable /run/firejail/x11 Remounting /proc and /proc/sys filesystems Remounting /sys directory Disable /sys/firmware Disable /sys/hypervisor Disable /sys/fs Disable /sys/module Disable /sys/power Disable /sys/kernel/debug Disable /sys/kernel/vmcoreinfo [...] ``` What exactly are you trying to do?
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
serialize_remounts_v2
landlock_v4
landlock
release-0.9.64
release-0.9.62
gitlab_ci
LTSbase
fred_ctests
docs
0.9.80
0.9.80-rc1
0.9.78
0.9.76
0.9.76-rc4
0.9.76-rc3
0.9.76-rc2
0.9.76-rc1
0.9.74
landlock-split
0.9.72
0.9.72rc1
0.9.70
0.9.68
0.9.68rc1
0.9.66
0.9.66rc1
0.9.64.4
0.9.64.2
0.9.64
0.9.64rc1
0.9.62.4
0.9.62.2
0.9.62
0.9.56.2-LTS
0.9.60
0.9.60-rc1
0.9.58.2
0.9.58
0.9.58-rc1
0.9.56-LTS-release
0.9.56-LTS
0.9.56
0.9.56-rc1
0.9.54
0.9.54-rc2
0.9.54-rc1
0.9.52
0.9.38.12
0.9.50
0.9.50-rc1
0.9.48
0.9.46
0.9.46-rc1
0.9.44.10
0.9.44.8
0.9.44.6
0.9.38.10
0.9.44.4
0.9.38.8
0.9.44.2
0.9.44
0.9.44-rc1
0.9.38.4
0.9.42
0.9.42-rc2
0.9.38.2
0.9.42-rc1
disable-globalcfg
0.9.40
0.9.40-rc1
0.9.38
0.9.38-rc1
0.9.36
0.9.36-rc1
0.9.34
0.9.34-rc1
0.9.32
0.9.32-rc1
0.9.30
0.9.30-rc1
Labels
Clear 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

Mirrored from GitHub Pull Request

  
question

   
question_old

   
removal

   
runtime-permissions

   
sandbox-ipc

   
security

   
stale

   
wiki

   
wiki

   
wontfix

   
wordpress

   
workaround
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
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
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#476
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?