mirror of
https://github.com/imthenachoman/How-To-Secure-A-Linux-Server.git
synced 2025-12-06 09:12:47 +01:00
Run applications in a sandbox with FireJail
This commit is contained in:
committed by
GitHub
parent
79ad5ed6f8
commit
e3edea1146
55
README.md
55
README.md
@@ -33,6 +33,7 @@ An evolving how-to guide for securing a Linux server that, hopefully, also teach
|
|||||||
- [The Basics](#the-basics)
|
- [The Basics](#the-basics)
|
||||||
- [Limit Who Can Use sudo](#limit-who-can-use-sudo)
|
- [Limit Who Can Use sudo](#limit-who-can-use-sudo)
|
||||||
- [Limit Who Can Use su](#limit-who-can-use-su)
|
- [Limit Who Can Use su](#limit-who-can-use-su)
|
||||||
|
- [Run applications in a sandbox with FireJail](#run-applications-in-a-sandbox-with-firejail)
|
||||||
- [NTP Client](#ntp-client)
|
- [NTP Client](#ntp-client)
|
||||||
- [Securing /proc](#securing-proc)
|
- [Securing /proc](#securing-proc)
|
||||||
- [Force Accounts To Use Secure Passwords](#force-accounts-to-use-secure-passwords)
|
- [Force Accounts To Use Secure Passwords](#force-accounts-to-use-secure-passwords)
|
||||||
@@ -871,6 +872,60 @@ su also lets accounts run commands as other accounts, including **root**. We wan
|
|||||||
|
|
||||||
([Table of Contents](#table-of-contents))
|
([Table of Contents](#table-of-contents))
|
||||||
|
|
||||||
|
### Run applications in a sandbox with FireJail
|
||||||
|
|
||||||
|
#### Why
|
||||||
|
|
||||||
|
It's absolutely better, for many applications, to run in a sandbox.
|
||||||
|
|
||||||
|
Browsers (even more the Closed Source ones) and eMail Clients are highly suggested.
|
||||||
|
|
||||||
|
#### Goals
|
||||||
|
|
||||||
|
- confine applications in a jail (few safe directories) and block access to the resto of the system
|
||||||
|
|
||||||
|
#### References
|
||||||
|
|
||||||
|
- Thanks to [FireJail](https://firejail.wordpress.com/)
|
||||||
|
|
||||||
|
#### Steps
|
||||||
|
|
||||||
|
1. Install the software:
|
||||||
|
|
||||||
|
``` bash
|
||||||
|
sudo apt install firejail firejail-profiles
|
||||||
|
```
|
||||||
|
|
||||||
|
Note: for Debian 10 Stable, official Backport is suggested:
|
||||||
|
|
||||||
|
``` bash
|
||||||
|
sudo apt install -t buster-backports firejail firejail-profiles
|
||||||
|
```
|
||||||
|
|
||||||
|
2. Allow an application (installed in `/usr/bin` or `/bin`) to run only in a sandbox (see few examples below here):
|
||||||
|
|
||||||
|
``` bash
|
||||||
|
sudo ln -s /usr/bin/firejail /usr/local/bin/google-chrome-stable
|
||||||
|
sudo ln -s /usr/bin/firejail /usr/local/bin/firefox
|
||||||
|
sudo ln -s /usr/bin/firejail /usr/local/bin/chromium
|
||||||
|
sudo ln -s /usr/bin/firejail /usr/local/bin/evolution
|
||||||
|
sudo ln -s /usr/bin/firejail /usr/local/bin/thunderbird
|
||||||
|
```
|
||||||
|
|
||||||
|
3. Run the application as usual (via terminal or launcher and check if is runnung in a jail:
|
||||||
|
|
||||||
|
``` bash
|
||||||
|
firejail --list
|
||||||
|
```
|
||||||
|
|
||||||
|
4. Allow a sandboxed app to run again as it wase before (example: firefox)
|
||||||
|
|
||||||
|
``` bash
|
||||||
|
sudo rm /usr/local/bin/firefox
|
||||||
|
```
|
||||||
|
|
||||||
|
([Table of Contents](#table-of-contents))
|
||||||
|
|
||||||
### NTP Client
|
### NTP Client
|
||||||
|
|
||||||
#### Why
|
#### Why
|
||||||
|
|||||||
Reference in New Issue
Block a user