1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
|
# Firejail
[![Build Status](https://gitlab.com/Firejail/firejail_ci/badges/master/pipeline.svg)](https://gitlab.com/Firejail/firejail_ci/pipelines/)
[![CodeQL](https://github.com/netblue30/firejail/workflows/CodeQL/badge.svg)](https://github.com/netblue30/firejail/actions?query=workflow%3ACodeQL)
[![Build CI](https://github.com/netblue30/firejail/workflows/Build%20CI/badge.svg)](https://github.com/netblue30/firejail/actions?query=workflow%3A%22Build+CI%22)
[![Packaging status](https://repology.org/badge/tiny-repos/firejail.svg)](https://repology.org/project/firejail/versions)
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. The software includes sandbox profiles for a number of more common Linux programs,
such as Mozilla Firefox, Chromium, VLC, Transmission etc.
The sandbox is lightweight, the overhead is low. There are no complicated configuration files to edit,
no socket connections open, no daemons running in the background. All security features are
implemented directly in Linux kernel and available on any Linux computer.
<table><tr>
<td>
<a href="https://odysee.com/@netblue30:9/firefox:c" target="_blank">
<img src="https://thumbs.odycdn.com/acf4b1c66737feb97640fb1d28a7daa6.png"
alt="Advanced Browser Security" width="240" height="142" border="10" /><br/>Advanced Browser Security</a>
</td>
<td>
<a href="https://odysee.com/@netblue30:9/nonet:7" target="_blank">
<img src="https://thumbs.odycdn.com/5be2964201c31689ee8f78cb9f35e89a.png"
alt="How To Disable Network Access" width="240" height="142" border="10" /><br/>How To Disable Network Access</a>
</td>
<td>
<a href="https://odysee.com/@netblue30:9/divested:2" target="_blank">
<img src="https://thumbs.odycdn.com/f30ece33a6547af9ae48244f4ba73028.png"
alt="Deep Dive" width="240" height="142" border="10" /><br/>Deep Dive</a>
</td>
</tr></table>
Project webpage: https://firejail.wordpress.com/
IRC: https://web.libera.chat/#firejail
Download and Installation: https://firejail.wordpress.com/download-2/
Features: https://firejail.wordpress.com/features-3/
Documentation: https://firejail.wordpress.com/documentation-2/
FAQ: https://github.com/netblue30/firejail/wiki/Frequently-Asked-Questions
Wiki: https://github.com/netblue30/firejail/wiki
GitLab-CI status: https://gitlab.com/Firejail/firejail_ci/pipelines/
Video Channel: https://odysee.com/@netblue30:9?order=new
Backup Video Channel: https://www.bitchute.com/profile/JSBsA1aoQVfW/
## Security vulnerabilities
We take security bugs very seriously. If you believe you have found one, please report it by emailing us at netblue30@protonmail.com
## Installing
### Debian
Debian stable (bullseye): We recommend to use the [backports](https://packages.debian.org/bullseye-backports/firejail) package.
### Ubuntu
For Ubuntu 18.04+ and derivatives (such as Linux Mint), users are **strongly advised** to use the [PPA](https://launchpad.net/~deki/+archive/ubuntu/firejail).
How to add and install from the PPA:
```sh
sudo add-apt-repository ppa:deki/firejail
sudo apt-get update
sudo apt-get install firejail firejail-profiles
```
Reason: The firejail package for Ubuntu 20.04 has been left vulnerable to CVE-2021-26910 for months after a patch for it was posted on Launchpad:
* [firejail version in Ubuntu 20.04 LTS is vulnerable to CVE-2021-26910](https://bugs.launchpad.net/ubuntu/+source/firejail/+bug/1916767)
See also <https://wiki.ubuntu.com/SecurityTeam/FAQ>:
> What software is supported by the Ubuntu Security team?
>
> Ubuntu is currently divided into four components: main, restricted, universe
> and multiverse. All binary packages in main and restricted are supported by
> the Ubuntu Security team for the life of an Ubuntu release, while binary
> packages in universe and multiverse are supported by the Ubuntu community.
Additionally, the PPA version is likely to be more recent and to contain more profile fixes.
See the following discussions for details:
* [Should I keep using the version of firejail available in my distro repos?](https://github.com/netblue30/firejail/discussions/4666)
* [How to install the latest version on Ubuntu and derivatives](https://github.com/netblue30/firejail/discussions/4663)
### Other
Firejail is included in a large number of Linux distributions.
You can also install one of the [released packages](http://sourceforge.net/projects/firejail/files/firejail), or clone Firejail’s source code from our Git repository and compile manually:
`````
$ git clone https://github.com/netblue30/firejail.git
$ cd firejail
$ ./configure && make && sudo make install-strip
`````
On Debian/Ubuntu you will need to install git and gcc compiler. AppArmor
development libraries and pkg-config are required when using `--apparmor`
./configure option:
`````
$ sudo apt-get install git build-essential libapparmor-dev pkg-config gawk
`````
For `--selinux` option, add libselinux1-dev (libselinux-devel for Fedora).
Detailed information on using firejail from git is available on the [wiki](https://github.com/netblue30/firejail/wiki/Using-firejail-from-git).
## Running the sandbox
To start the sandbox, prefix your command with `firejail`:
`````
$ firejail firefox # starting Mozilla Firefox
$ firejail transmission-gtk # starting Transmission BitTorrent
$ firejail vlc # starting VideoLAN Client
$ sudo firejail /etc/init.d/nginx start
`````
Run `firejail --list` in a terminal to list all active sandboxes. Example:
`````
$ firejail --list
1617:netblue:/usr/bin/firejail /usr/bin/firefox-esr
7719:netblue:/usr/bin/firejail /usr/bin/transmission-qt
7779:netblue:/usr/bin/firejail /usr/bin/galculator
7874:netblue:/usr/bin/firejail /usr/bin/vlc --started-from-file file:///home/netblue/firejail-whitelist.mp4
7916:netblue:firejail --list
`````
## Desktop integration
Integrate your sandbox into your desktop by running the following two commands:
`````
$ firecfg --fix-sound
$ sudo firecfg
`````
The first command solves some shared memory/PID namespace bugs in PulseAudio software prior to version 9.
The second command integrates Firejail into your desktop. You would need to logout and login back to apply
PulseAudio changes.
Start your programs the way you are used to: desktop manager menus, file manager, desktop launchers.
The integration applies to any program supported by default by Firejail. There are about 250 default applications
in current Firejail version, and the number goes up with every new release.
We keep the application list in [/etc/firejail/firecfg.config](https://github.com/netblue30/firejail/blob/master/src/firecfg/firecfg.config) file.
## Security profiles
Most Firejail command line options can be passed to the sandbox using profile files.
You can find the profiles for all supported applications in [/etc/firejail](https://github.com/netblue30/firejail/tree/master/etc) directory.
If you keep additional Firejail security profiles in a public repository, please give us a link:
* https://github.com/chiraag-nataraj/firejail-profiles
* https://github.com/triceratops1/fe
Use this issue to request new profiles: [#1139](https://github.com/netblue30/firejail/issues/1139)
You can also use this tool to get a list of syscalls needed by a program: [contrib/syscalls.sh](contrib/syscalls.sh).
We also keep a list of profile fixes for previous released versions in [etc-fixes](https://github.com/netblue30/firejail/tree/master/etc-fixes) directory.
## Latest released version: 0.9.70
## Current development version: 0.9.71
Milestone page: https://github.com/netblue30/firejail/milestone/1
### Modified functionality
* modif: removed cgroups commands (#5190)
* modif: changed --disable-firetunnel into --enable-firetunnel in configure.ac (#5190)
* modif: disabled chroot by default in /etc/firejail/firejail.config (#5190)
* modif: shell none set as default (#5190)
* modif: removed --shell= (#5190)
* modif: private-lib disabled by default in /etc/firejail/firejail.config (#5190)
### Restrict namespaces
`````
--restrict-namespaces
Install a seccomp filter that blocks attempts to create new
cgroup, ipc, net, mount, pid, time, user or uts namespaces.
Example:
$ firejail --restrict-namespaces
--restrict-namespaces=cgroup,ipc,net,mnt,pid,time,user,uts
Install a seccomp filter that blocks attempts to create any of
the specified namespaces. The filter examines the arguments of
clone, unshare and setns system calls and returns error EPERM to
the process (or kills it or logs the attempt, see --seccomp-er‐
ror-action below) if necessary. Note that the filter is not able
to examine the arguments of clone3 system calls, and always re‐
sponds to these calls with error ENOSYS.
Example:
$ firejail --restrict-namespaces=user,net
`````
### Support for custom AppArmor profiles
`````
--apparmor
Enable AppArmor confinement with the "firejail-default" AppArmor
profile. For more information, please see APPARMOR section be‐
low.
--apparmor=profile_name
Enable AppArmor confinement with a custom AppArmor profile.
Note that profile in question must already be loaded into the
kernel. For more information, please see APPARMOR section be‐
`````
### Landlock support - EXPERIMENTAL
For the next release (0.9.72), landlock support is experimental. It is disabled in the normal build
or in the executable archives we provide. It will be "officially" released
in 0.9.74, sometime early next year. For now, use --enable-landlock during software compile:
`````
$ ./configure --enable-landlock
`````
The functionality is segragated with ifdefs in the code, at times it might not even compile!
Work in progress, the interface described in the man page below could change.
`````
--landlock
Create a Landlock ruleset (if it doesn't already exist) and add
basic access rules to it. See LANDLOCK section for more informa‐
tion.
--landlock.proc=no|ro|rw
Add an access rule for /proc directory (read-only if set to ro
and read-write if set to rw). The access rule for /proc is added
after this directory is set up in the sandbox. Access rules for
/proc set up with other Landlock-related command-line options
have no effect.
--landlock.read=path
Create a Landlock ruleset (if it doesn't already exist) and add
a read access rule for path.
--landlock.write=path
Create a Landlock ruleset (if it doesn't already exist) and add
a write access rule for path.
--landlock.special=path
Create a Landlock ruleset (if it doesn't already exist) and add
a permission rule to create FIFO pipes, Unix domain sockets and
block devices beneath given path.
--landlock.execute=path
Create a Landlock ruleset (if it doesn't already exist) and add
an execution permission rule for path.
Example:
$ firejail --landlock.read=/ --landlock.write=/home --land‐
lock.execute=/usr
LANDLOCK
Landlock is a Linux security module first introduced in the 5.13 ver‐
sion of Linux kernel. It allows unprivileged processes to restrict
their access to the filesystem. Once imposed, these restrictions can
never be removed, and all child processes created by a Landlock-re‐
stricted processes inherit these restrictions. Firejail supports Land‐
lock as an additional sandboxing feature. It can be used to ensure that
a sandboxed application can only access files and directories that it
was explicitly allowed to access. Firejail supports populating the
ruleset with both basic set of rules and with custom set of rules. Ba‐
sic set of rules allows read-only access to /bin, /dev, /etc, /lib,
/opt, /proc, /usr and /var, read-write access to the home directory,
and allows execution of binaries located in /bin, /opt and /usr.
Important notes:
- A process can install a Landlock ruleset only if it has either
CAP_SYS_ADMIN in its effective capability set, or the "No New
Privileges" restriction enabled. Because of this, enabling the
Landlock feature will also cause Firejail to enable the "No New
Privileges" restriction, regardless of the profile or the
--no-new-privs command line option.
- Access to the /proc directory is managed through the --land‐
lock.proc command line option.
- Access to the /etc directory is automatically allowed. To
override this, use the --writable-etc command line option. You
can also use the --private-etc option to restrict access to the
/etc directory.
To enable Landlock self-restriction on top of your current Firejail se‐
curity features, pass --landlock flag to Firejail command line. You can
also use --landlock.read, --landlock.write, --landlock.special and
--landlock.execute options together with --landlock or instead of it.
Example:
$ firejail --landlock --landlock.read=/media --landlock.proc=ro
mc
`````
### Profile Statistics
A small tool to print profile statistics. Compile and install as usual. The tool is installed in /usr/lib/firejail directory.
Run it over the profiles in /etc/profiles:
```
$ /usr/lib/firejail/profstats /etc/firejail/*.profile
No include .local found in /etc/firejail/noprofile.profile
Warning: multiple caps in /etc/firejail/transmission-daemon.profile
Stats:
profiles 1196
include local profile 1195 (include profile-name.local)
include globals 1169 (include globals.local)
blacklist ~/.ssh 1067 (include disable-common.inc)
seccomp 1087
capabilities 1190
noexec 1075 (include disable-exec.inc)
noroot 995
memory-deny-write-execute 269
apparmor 713
private-bin 695
private-dev 1045
private-etc 542
private-lib 70
private-tmp 918
whitelist home directory 575
whitelist var 858 (include whitelist-var-common.inc)
whitelist run/user 1164 (include whitelist-runuser-common.inc
or blacklist ${RUNUSER})
whitelist usr/share 630 (include whitelist-usr-share-common.inc
net none 404
dbus-user none 677
dbus-user filter 123
dbus-system none 837
dbus-system filter 12
```
### New profiles:
onionshare, onionshare-cli, opera-developer, songrec, gdu, makedeb, lbry-viewer, tuir,
|