other versions
- jessie-backports 0.9.44.8-2~bpo8+1
- stretch 0.9.44.8-2
- testing 0.9.58.2-1
- stretch-backports 0.9.58.2-1~bpo9+1
- unstable 0.9.58.2-1
FIREJAIL(1) | firejail man page | FIREJAIL(1) |
NAME¶
Firejail - Linux namespaces sandbox programSYNOPSIS¶
Start a sandbox:firejail [OPTIONS] [program and arguments]
File transfer from an existing sandbox
firejail {--ls | --get | --put} dir_or_filename
Network traffic shaping for an existing sandbox:
firejail --bandwidth={name|pid} bandwidth-command
Monitoring:
firejail {--list | --netstats | --top | --tree}
Miscellaneous:
firejail {-? | --debug-caps | --debug-errnos |
--debug-syscalls | --debug-protocols | --help | --version}
DESCRIPTION¶
Firejail is a SUID sandbox program that reduces the risk of security breaches by restricting the running environment of untrusted applications using Linux namespaces, seccomp-bpf and Linux capabilities. It allows a process and all its descendants to have their own private view of the globally shared kernel resources, such as the network stack, process table, mount table. Firejail can work in a SELinux or AppArmor environment, and it is integrated with Linux Control Groups. Written in C with virtually no dependencies, the software runs on any Linux computer with a 3.x kernel version or newer. It can sandbox any type of processes: servers, graphical applications, and even user login sessions. Firejail allows the user to manage application security using security profiles. Each profile defines a set of permissions for a specific application or group of applications. The software includes security profiles for a number of more common Linux programs, such as Mozilla Firefox, Chromium, VLC, Transmission etc.USAGE¶
Without any options, the sandbox consists of a filesystem build in a new mount namespace, and new PID and UTS namespaces. IPC, network and user namespaces can be added using the command line options. The default Firejail filesystem is based on the host filesystem with the main system directories mounted read-only. These directories are /etc, /var, /usr, /bin, /sbin, /lib, /lib32, /libx32 and /lib64. Only /home and /tmp are writable. As it starts up, Firejail tries to find a security profile based on the name of the application. If an appropriate profile is not found, Firejail will use a default profile. The default profile is quite restrictive. In case the application doesn't work, use --noprofile option to disable it. For more information, please see SECURITY PROFILES section below. If a program argument is not specified, Firejail starts /bin/bash shell. Examples: $ firejail [OPTIONS] # starting a /bin/bash shell $ firejail [OPTIONS] firefox # starting Mozilla Firefox # sudo firejail [OPTIONS] /etc/init.d/nginx startOPTIONS¶
- --
- Signal the end of options and disables further option processing.
- --allow-debuggers
- Allow tools such as strace and gdb inside the sandbox. This option is only
available when running on Linux kernels 4.8 or newer - a kernel bug in
ptrace system call allows a full bypass of the seccomp filter.
- --allusers
- All user home directories are visible inside the sandbox. By default, only
current user home directory is visible.
- --apparmor
- Enable AppArmor confinement. For more information, please see APPARMOR section below.
- --appimage
- Sandbox an AppImage (http://appimage.org/) application.
- --audit
- Audit the sandbox, see AUDIT section for more details.
- --audit=test-program
- Audit the sandbox, see AUDIT section for more details.
- --bandwidth=name|pid
- Set bandwidth limits for the sandbox identified by name or PID, see TRAFFIC SHAPING section for more details.
- --bind=filename1,filename2
- Mount-bind filename1 on top of filename2. This option is only available
when running as root.
- --blacklist=dirname_or_filename
- Blacklist directory or file.
- -c
- Execute command and exit.
- --caps
- Linux capabilities is a kernel feature designed to split up the root
privilege into a set of distinct privileges. These privileges can be
enabled or disabled independently, thus restricting what a process running
as root can do in the system.
By default root programs run with all capabilities enabled. --caps option
disables the following capabilities: CAP_SYS_MODULE, CAP_SYS_RAWIO,
CAP_SYS_BOOT, CAP_SYS_NICE, CAP_SYS_TTY_CONFIG, CAP_SYSLOG, CAP_MKNOD,
CAP_SYS_ADMIN. The filter is applied to all processes started in the
sandbox.
- --caps.drop=all
- Drop all capabilities for the processes running in the sandbox. This
option is recommended for running GUI programs or any other program that
doesn't require root privileges. It is a must-have option for sandboxing
untrusted programs installed from unofficial sources - such as games, Java
programs, etc.
- --caps.drop=capability,capability,capability
- Define a custom blacklist Linux capabilities filter.
- --caps.keep=capability,capability,capability
- Define a custom whitelist Linux capabilities filter.
- --caps.print=name|pid
- Print the caps filter for the sandbox identified by name or by PID.
- --cgroup=tasks-file
- Place the sandbox in the specified control group. tasks-file is the full
path of cgroup tasks file.
- --chroot=dirname
- Chroot the sandbox into a root filesystem. Unlike the regular filesystem
container, the system directories are mounted read-write. If the sandbox
is started as a regular user, default seccomp and capabilities filters are
enabled. This option is not available on Grsecurity systems.
- --cpu=cpu-number,cpu-number,cpu-number
- Set CPU affinity.
- --cpu.print=name|pid
- Print the CPU cores in use by the sandbox identified by name or by PID.
- --csh
- Use /bin/csh as default user shell.
- --debug
- Print debug messages.
- --debug-blacklists
- Debug blacklisting.
- --debug-caps
- Print all recognized capabilities in the current Firejail software build
and exit.
- --debug-check-filename
- Debug filename checking.
- --debug-errnos
- Print all recognized error numbers in the current Firejail software build
and exit.
- --debug-protocols
- Print all recognized protocols in the current Firejail software build and
exit.
- --debug-syscalls
- Print all recognized system calls in the current Firejail software build
and exit.
- --debug-whitelists
- Debug whitelisting.
- --defaultgw=address
- Use this address as default gateway in the new network namespace.
- --dns=address
- Set a DNS server for the sandbox. Up to three DNS servers can be defined.
Use this option if you don't trust the DNS setup on your network.
- --dns.print=name|pid
- Print DNS configuration for a sandbox identified by name or by PID.
- --env=name=value
- Set environment variable in the new sandbox.
- --force
- By default, if Firejail is started in an existing sandbox, it will run the program in a bash shell. This option disables this behavior, and attempts to start Firejail in the existing sandbox. There could be lots of reasons for it to fail, for example if the existing sandbox disables admin capabilities, SUID binaries, or if it runs seccomp.
- --fs.print=name|print
- Print the filesystem log for the sandbox identified by name or by PID.
- --get=name|pid filename
- Get a file from sandbox container, see FILE TRANSFER section for more details.
- -?, --help
- Print options end exit.
- --hostname=name
- Set sandbox hostname.
- --ignore=command
- Ignore command in profile file.
- --interface=interface
- Move interface in a new network namespace. Up to four --interface options
can be specified. Note: wlan devices are not supported for this option.
- --ip=address
- Assign IP addresses to the last network interface defined by a --net
option. A default gateway is assigned by default.
- --ip=none
- No IP address and no default gateway are configured for the last interface
defined by a --net option. Use this option in case you intend to start an
external DHCP client in the sandbox.
- --ip6=address
- Assign IPv6 addresses to the last network interface defined by a --net
option.
- --iprange=address,address
- Assign an IP address in the provided range to the last network interface
defined by a --net option. A default gateway is assigned by default.
- --ipc-namespace
- Enable a new IPC namespace if the sandbox was started as a regular user.
IPC namespace is enabled by default for sandboxes started as root.
- --join=name|pid
- Join the sandbox identified by name or by PID. By default a /bin/bash
shell is started after joining the sandbox. If a program is specified, the
program is run in the sandbox. If --join command is issued as a regular
user, all security filters are configured for the new process the same
they are configured in the sandbox. If --join command is issued as root,
the security filters, cgroups and cpus configurations are not applied to
the process joining the sandbox.
- --join-filesystem=name|pid
- Join the mount namespace of the sandbox identified by name or PID. By default a /bin/bash shell is started after joining the sandbox. If a program is specified, the program is run in the sandbox. This command is available only to root user. Security filters, cgroups and cpus configurations are not applied to the process joining the sandbox.
- --join-network=name|PID
- Join the network namespace of the sandbox identified by name. By default a
/bin/bash shell is started after joining the sandbox. If a program is
specified, the program is run in the sandbox. This command is available
only to root user. Security filters, cgroups and cpus configurations are
not applied to the process joining the sandbox. Example:
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
link/ether 76:58:14:42:78:e4 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.158/24 brd 192.168.1.255 scope global eth0-1931
valid_lft forever preferred_lft forever
inet6 fe80::7458:14ff:fe42:78e4/64 scope link
valid_lft forever preferred_lft forever
- --join-or-start=name
- Join the sandbox identified by name or start a new one. Same as
"firejail --join=name" if sandbox with specified name exists,
otherwise same as "firejail --name=name ..."
- --ls=name|pid dir_or_filename
- List files in sandbox container, see FILE TRANSFER section for more details.
- --list
- List all sandboxes, see MONITORING section for more details.
- --mac=address
- Assign MAC addresses to the last network interface defined by a --net
option.
- --machine-id
- Spoof id number in /etc/machine-id file - a new random id is generated
inside the sandbox.
- --mtu=number
- Assign a MTU value to the last network interface defined by a --net
option.
- --name=name
- Set sandbox name. Several options, such as --join and --shutdown, can use
this name to identify a sandbox.
- --net=bridge_interface
- Enable a new network namespace and connect it to this bridge interface.
Unless specified with option --ip and --defaultgw, an IP address and a
default gateway will be assigned automatically to the sandbox. The IP
address is verified using ARP before assignment. The address configured as
default gateway is the bridge device IP address. Up to four --net bridge
devices can be defined. Mixing bridge and macvlan devices is allowed.
- --net=ethernet_interface
- Enable a new network namespace and connect it to this ethernet interface
using the standard Linux macvlan driver. Unless specified with option --ip
and --defaultgw, an IP address and a default gateway will be assigned
automatically to the sandbox. The IP address is verified using ARP before
assignment. The address configured as default gateway is the default
gateway of the host. Up to four --net devices can be defined. Mixing
bridge and macvlan devices is allowed. Note: wlan devices are not
supported for this option.
- --net=none
- Enable a new, unconnected network namespace. The only interface available
in the new namespace is a new loopback interface (lo). Use this option to
deny network access to programs that don't really need network access.
- --netfilter
- Enable a default client network filter in the new network namespace. New
network namespaces are created using --net option. If a new network
namespaces is not created, --netfilter option does nothing. The default
filter is as follows:
- --netfilter=filename
- Enable the network filter specified by filename in the new network
namespace. The filter file format is the format of iptables-save and
iptable-restore commands. New network namespaces are created using --net
option. If a new network namespaces is not created, --netfilter option
does nothing.
- --netfilter6=filename
- Enable the IPv6 network filter specified by filename in the new network namespace. The filter file format is the format of ip6tables-save and ip6table-restore commands. New network namespaces are created using --net option. If a new network namespaces is not created, --netfilter6 option does nothing.
- --netstats
- Monitor network namespace statistics, see MONITORING section for
more details.
- --nice=value
- Set nice value for all processes running inside the sandbox. Only root may
specify a negative value.
- --no3d
- Disable 3D hardware acceleration.
- --noblacklist=dirname_or_filename
- Disable blacklist for this directory or file.
- --noexec=dirname_or_filename
- Remount directory or file noexec, nodev and nosuid.
- --nogroups
- Disable supplementary groups. Without this option, supplementary groups
are enabled for the user starting the sandbox. For root user supplementary
groups are always disabled.
- --noprofile
- Do not use a security profile.
- --noroot
- Install a user namespace with a single user - the current user. root user
does not exist in the new namespace. This option requires a Linux kernel
version 3.8 or newer. The option is not supported for --chroot and
--overlay configurations, or for sandboxes started as root.
- --nonewprivs
- Sets the NO_NEW_PRIVS prctl. This ensures that child processes cannot acquire new privileges using execve(2); in particular, this means that calling a suid binary (or one with file capabilities) does not result in an increase of privilege. This option is enabled by default if seccomp filter is activated.
- --nosound
- Disable sound system.
- --output=logfile
- stdout logging and log rotation. Copy stdout and stderr to logfile, and
keep the size of the file under 500KB using log rotation. Five files with
prefixes .1 to .5 are used in rotation.
- --overlay
- Mount a filesystem overlay on top of the current filesystem. Unlike the
regular filesystem container, the system directories are mounted
read-write. All filesystem modifications go into the overlay. The overlay
is stored in $HOME/.firejail/<PID> directory.
- --overlay-named=name
- Mount a filesystem overlay on top of the current filesystem. Unlike the
regular filesystem container, the system directories are mounted
read-write. All filesystem modifications go into the overlay. The overlay
is stored in $HOME/.firejail/<NAME> directory. The created overlay
can be reused between multiple sessions.
- --overlay-tmpfs
- Mount a filesystem overlay on top of the current filesystem. All
filesystem modifications go into the overlay, and are discarded when the
sandbox is closed.
- --overlay-clean
- Clean all overlays stored in $HOME/.firejail directory. Overlays created
with --overlay-path=path outside $HOME/.firejail will not be deleted.
- --private
- Mount new /root and /home/user directories in temporary filesystems. All
modifications are discarded when the sandbox is closed.
- --private=directory
- Use directory as user home.
- --private-home=file,directory
- Build a new user home in a temporary filesystem, and copy the files and
directories in the list in the new home. All modifications are discarded
when the sandbox is closed.
- --private-bin=file,file
- Build a new /bin in a temporary filesystem, and copy the programs in the
list. If no listed file is found, /bin directory will be empty. The same
directory is also bind-mounted over /sbin, /usr/bin, /usr/sbin and
/usr/local/bin. All modifications are discarded when the sandbox is
closed.
- --private-dev
- Create a new /dev directory. Only dri, null, full, zero, tty, pts, ptmx,
random, snd, urandom, log and shm devices are available.
- --private-etc=file,directory
- Build a new /etc in a temporary filesystem, and copy the files and
directories in the list. If no listed file is found, /etc directory will
be empty. All modifications are discarded when the sandbox is closed.
- --private-tmp
- Mount an empty temporary filesystem on top of /tmp directory.
- --profile=filename
- Load a custom security profile from filename. For filename use an absolute
path or a path relative to the current path. For more information, see
SECURITY PROFILES section below.
- --profile-path=directory
- Use this directory to look for profile files. Use an absolute path or a
path in the home directory starting with ~/. For more information, see
SECURITY PROFILES section below and RELOCATING PROFILE FILES
in man 5 firejail-profile.
- --protocol=protocol,protocol,protocol
- Enable protocol filter. The filter is based on seccomp and checks the
first argument to socket system call. Recognized values: unix, inet,
inet6, netlink and packet. This option is not supported for i386
architecture.
- --protocol.print=name|pid
- Print the protocol filter for the sandbox identified by name or PID.
- --put=name|pid src-filename dest-filename
- Put a file in sandbox container, see FILE TRANSFER section for more details.
- --quiet
- Turn off Firejail's output.
- --read-only=dirname_or_filename
- Set directory or file read-only.
- --read-write=dirname_or_filename
- Set directory or file read-write. Only files or directories belonging to
the current user are allowed for this operation. Example:
- --rlimit-fsize=number
- Set the maximum file size that can be created by a process.
- --rlimit-nofile=number
- Set the maximum number of files that can be opened by a process.
- --rlimit-nproc=number
- Set the maximum number of processes that can be created for the real user ID of the calling process.
- --rlimit-sigpending=number
- Set the maximum number of pending signals for a process.
- --rmenv=name
- Remove environment variable in the new sandbox.
- --scan
- ARP-scan all the networks from inside a network namespace. This makes it
possible to detect macvlan kernel device drivers running on the current
host.
- --seccomp
- Enable seccomp filter and blacklist the syscalls in the default list. The
default list is as follows: mount, umount2, ptrace, kexec_load,
kexec_file_load, name_to_handle_at, open_by_handle_at, create_module,
init_module, finit_module, delete_module, iopl, ioperm, ioprio_set,
swapon, swapoff, syslog, process_vm_readv, process_vm_writev,
sysfs,_sysctl, adjtimex, clock_adjtime, lookup_dcookie, perf_event_open,
fanotify_init, kcmp, add_key, request_key, keyctl, uselib, acct,
modify_ldt, pivot_root, io_setup, io_destroy, io_getevents, io_submit,
io_cancel, remap_file_pages, mbind, get_mempolicy, set_mempolicy,
migrate_pages, move_pages, vmsplice, chroot, tuxcall, reboot, mfsservctl
and get_kernel_syms.
- --seccomp=syscall,syscall,syscall
- Enable seccomp filter, blacklist the default list and the syscalls
specified by the command.
- --seccomp.drop=syscall,syscall,syscall
- Enable seccomp filter, and blacklist the syscalls specified by the
command.
- --seccomp.keep=syscall,syscall,syscall
- Enable seccomp filter, and whitelist the syscalls specified by the
command.
- --seccomp.<errno>=syscall,syscall,syscall
- Enable seccomp filter, and return errno for the syscalls specified by the
command.
- --seccomp.print=name|PID
- Print the seccomp filter for the sandbox identified by name or PID.
VALIDATE_ARCHITECTURE
EXAMINE_SYSCALL
BLACKLIST 165 mount
BLACKLIST 166 umount2
BLACKLIST 101 ptrace
BLACKLIST 246 kexec_load
BLACKLIST 304 open_by_handle_at
BLACKLIST 175 init_module
BLACKLIST 176 delete_module
BLACKLIST 172 iopl
BLACKLIST 173 ioperm
BLACKLIST 167 swapon
BLACKLIST 168 swapoff
BLACKLIST 103 syslog
BLACKLIST 310 process_vm_readv
BLACKLIST 311 process_vm_writev
BLACKLIST 133 mknod
BLACKLIST 139 sysfs
BLACKLIST 156 _sysctl
BLACKLIST 159 adjtimex
BLACKLIST 305 clock_adjtime
BLACKLIST 212 lookup_dcookie
BLACKLIST 298 perf_event_open
BLACKLIST 300 fanotify_init
RETURN_ALLOW
- --shell=none
- Run the program directly, without a user shell.
- --shell=program
- Set default user shell. Use this shell to run the application using -c
shell option. For example "firejail --shell=/bin/dash firefox"
will start Mozilla Firefox as "/bin/dash -c firefox". By default
Bash shell (/bin/bash) is used. Options such as --zsh and --csh can also
set the default shell.
- --shutdown=name|PID
- Shutdown the sandbox identified by name or PID.
- --tmpfs=dirname
- Mount a tmpfs filesystem on directory dirname. This option is available
only when running the sandbox as root.
- --top
- Monitor the most CPU-intensive sandboxes, see MONITORING section
for more details.
- --trace
- Trace open, access and connect system calls.
- --tracelog
- This option enables auditing blacklisted files and directories. A message
is sent to syslog in case the file or the directory is accessed.
- --tree
- Print a tree of all sandboxed processes, see MONITORING section for
more details.
11904:netblue:iceweasel
11957:netblue:/usr/lib/iceweasel/plugin-container
11970:netblue:transmission-gtk
- --version
- Print program version and exit.
- --veth-name=name
- Use this name for the interface connected to the bridge for
--net=bridge_interface commands, instead of the default one.
- --whitelist=dirname_or_filename
- Whitelist directory or file. A temporary file system is mounted on the top
directory, and the whitelisted files are mount-binded inside.
Modifications to whitelisted files are persistent, everything else is
discarded when the sandbox is closed. The top directory could be user
home, /dev, /media, /mnt, /opt, /srv, /var, and /tmp.
- --writable-etc
- Mount /etc directory read-write.
- --writable-var
- Mount /var directory read-write.
- --x11
- Sandbox the application using Xpra, Xephyr or Xorg security extension. The
sandbox will prevents screenshot and keylogger applications started inside
the sandbox from accessing clients running outside the sandbox. Firejail
will try first Xpra, and if Xpra is not installed on the system, it will
try to find Xephyr. If all fails, Firejail will not attempt to use X11
security extension.
- --x11=none
- Blacklist /tmp/.X11-unix directory, ${HOME}/.Xauthority and the file specified in ${XAUTHORITY} environment variable. Remove DISPLAY and XAUTHORITY environment variables. Stop with error message if X11 abstract socket will be accessible in jail.
- --x11=xephyr
- Start Xephyr and attach the sandbox to this server. Xephyr is a display
server implementing the X11 display server protocol. A network namespace
needs to be instantiated in order to deny access to X11 abstract Unix
domain socket.
- --x11=xorg
- Sandbox the application using the untrusted mode implemented by X11
security extension. The extension is available in Xorg package and it is
installed by default on most Linux distributions. It provides support for
a simple trusted/untrusted connection model. Untrusted clients are
restricted in certain ways to prevent them from reading window contents of
other clients, stealing input events, etc.
The untrusted mode has several limitations. A lot of regular programs assume
they are a trusted X11 clients and will crash or lock up when run in
untrusted mode. Chromium browser and xterm are two examples. Firefox and
transmission-gtk seem to be working fine. A network namespace is not
required for this option.
- --x11=xpra
- Start Xpra (http://xpra.org) and attach the sandbox to this server. Xpra
is a persistent remote display server and client for forwarding X11
applications and desktop screens. A network namespace needs to be
instantiated in order to deny access to X11 abstract Unix domain socket.
- --zsh
- Use /usr/bin/zsh as default user shell.
DESKTOP INTEGRATION¶
A symbolic link to /usr/bin/firejail under the name of a program, will start the program in Firejail sandbox. The symbolic link should be placed in the first $PATH position. On most systems, a good place is /usr/local/bin directory. Example:1190:netblue:firejail firefox
1220:netblue:/bin/sh -c "/usr/lib/firefox/firefox"
1221:netblue:/usr/lib/firefox/firefox
APPARMOR¶
- AppArmor support is disabled by default at compile time. Use --enable-apparmor configuration option to enable it:
-
- During software install, a generic AppArmor profile file, firejail-default, is placed in /etc/apparmor.d directory. The profile needs to be loaded into the kernel by running the following command as root:
-
- The installed profile tries to replicate some advanced security features inspired by kernel-based Grsecurity:
-
- To enable AppArmor confinement on top of your current Firejail security features, pass --apparmor flag to Firejail command line. You can also include apparmor command in a Firejail profile file. Example:
-
FILE TRANSFER¶
These features allow the user to inspect the filesystem container of an existing sandbox and transfer files from the container to the host filesystem.- --get=name|pid filename
- Retrieve the container file and store it on the host in the current working directory. The container is specified by name or PID. This option is not available for sandboxes using --chroot.
- --ls=name|pid dir_or_filename
- List container files. The container is specified by name or PID.
- --put=name|pid src-filename dest-filename
- Put src-filename in sandbox container. The container is specified by name or PID. This option is not available for sandboxes using --chroot.
- Examples:
-
TRAFFIC SHAPING¶
Network bandwidth is an expensive resource shared among all sandboxes running on a system. Traffic shaping allows the user to increase network performance by controlling the amount of data that flows into and out of the sandboxes. Firejail implements a simple rate-limiting shaper based on Linux command tc. The shaper works at sandbox level, and can be used only for sandboxes configured with new network namespaces. Set rate-limits: $ firejail --bandwidth=name|pid set network download upload Clear rate-limits: $ firejail --bandwidth=name|pid clear network Status: $ firejail --bandwidth=name|pid status where:AUDIT¶
Audit feature allows the user to point out gaps in security profiles. The implementation replaces the program to be sandboxed with a test program. By default, we use faudit program distributed with Firejail. A custom test program can also be supplied by the user. Examples: Running the default audit program:MONITORING¶
Option --list prints a list of all sandboxes. The format for each process entry is as follows: PID:USER:Command Option --tree prints the tree of processes running in the sandbox. The format for each process entry is as follows: PID:USER:Command Option --top is similar to the UNIX top command, however it applies only to sandboxes. Option --netstats prints network statistics for active sandboxes installing new network namespaces. Listed below are the available fields (columns) in alphabetical order for --top and --netstat options:- Command
- Command used to start the sandbox.
- CPU%
- CPU usage, the sandbox share of the elapsed CPU time since the last screen update
- PID
- Unique process ID for the task controlling the sandbox.
- Prcs
- Number of processes running in sandbox, including the controlling process.
- RES
- Resident Memory Size (KiB), sandbox non-swapped physical memory. It is a sum of the RES values for all processes running in the sandbox.
- RX(KB/s)
- Network receive speed.
- SHR
- Shared Memory Size (KiB), it reflects memory shared with other processes. It is a sum of the SHR values for all processes running in the sandbox, including the controlling process.
- TX(KB/s)
- Network transmit speed.
- Uptime
- Sandbox running time in hours:minutes:seconds format.
- User
- The owner of the sandbox.
SECURITY PROFILES¶
Several command line options can be passed to the program using profile files. Firejail chooses the profile file as follows: 1. If a profile file is provided by the user with --profile option, the profile file is loaded. Example:$ firejail --profile=/home/netblue/icecat.profile icecat
Reading profile /home/netblue/icecat.profile
[...]
2. If a profile file with the same name as the application is present in
~/.config/firejail directory or in /etc/firejail, the profile is loaded.
~/.config/firejail takes precedence over /etc/firejail. Example:
$ firejail icecat
Command name #icecat#
Found icecat profile in /home/netblue/.config/firejail directory
Reading profile /home/netblue/.config/firejail/icecat.profile
[...]
3. Use default.profile file if the sandbox is started by a regular user, or
server.profile file if the sandbox is started by root. Firejail looks for
these files in ~/.config/firejail directory, followed by /etc/firejail
directory. To disable default profile loading, use --noprofile command option.
Example:
$ firejail
Reading profile /etc/firejail/default.profile
Parent pid 8553, child pid 8554
Child process initialized
[...]
$ firejail --noprofile
Parent pid 8553, child pid 8554
Child process initialized
[...]
See man 5 firejail-profile for profile file syntax information.
RESTRICTED SHELL¶
To configure a restricted shell, replace /bin/bash with /usr/bin/firejail in /etc/passwd file for each user that needs to be restricted. Alternatively, you can specify /usr/bin/firejail in adduser command: adduser --shell /usr/bin/firejail username Additional arguments passed to firejail executable upon login are declared in /etc/firejail/login.users file.EXAMPLES¶
- firejail
- Sandbox a regular /bin/bash session.
- firejail firefox
- Start Mozilla Firefox.
- firejail --debug firefox
- Debug Firefox sandbox.
- firejail --private firefox
- Start Firefox with a new, empty home directory.
- firejail --net=none vlc
- Start VLC in an unconnected network namespace.
- firejail --net=eth0 firefox
- Start Firefox in a new network namespace. An IP address is assigned automatically.
- firejail --net=br0 --ip=10.10.20.5 --net=br1 --net=br2
- Start a /bin/bash session in a new network namespace and connect it to br0, br1, and br2 host bridge devices. IP addresses are assigned automatically for the interfaces connected to br1 and b2
- firejail --list
- List all sandboxed processes.
LICENSE¶
This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version. Homepage: http://firejail.wordpress.comSEE ALSO¶
firemon(1), firecfg(1), firejail-profile(5), firejail-login(5)May 2017 | 0.9.44.8 |