Need help with oz?
Click the “chat” button below for chat support from the developer who created it, or find similar developers for support.

About the developer

425 Stars 53 Forks Other 833 Commits 69 Opened issues


OZ: a sandboxing system targeting everyday workstation applications

Services available


Need anything else?

Contributors list


Oz is a sandboxing system targeting everyday workstation applications. It acts as a wrapper around application executables for completely transparent user operations. It achieves process containment through the use of Linux Namespaces, Seccomp filters, Capabilities, and X11 restriction using Xpra. It has built-in support with automatic configuration of bridge mode networking and also support working with contained network environment using the built in connection forwarding proxy.

See the wiki for the complete technical documentation.


OZ Sandbox Evince Demo


Please note that Oz is currently under major development and still at a very alpha stage. As of this writing some features are not yet available in the public master branch. It is not intended for use in multi-users systems. Use it at your own risk!


You can easily build a debian package from the latest tagged release:

$ sudo apt-get install golang xpra bridge-utils ebtables libacl1 libacl1-dev dh-golang dh-systemd git-buildpackage
$ git clone -b debian
$ cd oz
### To Build from stable
$ gbp buildpackage -us -uc
### To Build from strict-etc
$ gbp buildpackage -us -uc --git-upstream-branch=strict-etc
### Once you are ready to install and have no important unsaved content in Oz windows
$ sudo dpkg -i /tmp/build-area/oz-daemon_.deb
$ sudo paxrat
$ sudo systemctl restart oz-daemon.service

Or to build it manually:


Currently Oz only works and is only tested for Debian (>= jessie). As of this writing it does not work in Ubuntu. While it has been minimally tested under Fedora, there doesn't exist an RPM equivalent to

which allows to conveniantly wrap executables of existing program. For seccomp filters you need at least kernel version 3.17. We recommend using Debian stretch with a 4.0+ grsecurity patched kernel.

It is highly recommend that you run it in conjunction with grsecurity.


$ sudo apt-get install golang xpra bridge-utils ebtables libacl1

You need golang version 1.4.

You must also have the

kernel module loaded to use bridge network mode.


If you are using grsecurity you will need to disable the following kernel options permanently via the sysctl interface or by echoing values to files in

kernel.grsecurity.chroot_caps = 0
kernel.grsecurity.chroot_deny_chmod = 0
kernel.grsecurity.chroot_deny_mount = 0

See Grsecurity/Appendix/Sysctl Options for information on setting grsecurity sysctl options.

Network Manager

If you are using Network-Manager you need to make sure to exclude the bridge interface. To do so a file must be created in


[keyfile] unmanaged-devices=mac:6a:a8:2e:56:e8:9c;interface-name:oz0

If this file is missing

will output a warning but it may fail to setup bridge networking.

Bridge networking

Bridge networking is automatically configured by Oz, but you will need to setup at minimum a few iptables masquerading rules and ebtables isolation rules as follows (adjusted with the name of the interfaces):

sudo ebtables -P FORWARD DROP
sudo ebtables -F FORWARD
sudo ebtables -A FORWARD -i oz0 -j ACCEPT
sudo ebtables -A FORWARD -o oz0 -j ACCEPT

IP Forwarding must be enabled (do this as root):

# echo 1 >/proc/sys/net/ipv4/ip_forward


  1. To setup a GOPATH for Oz, run the following commands (or you can use your existing GOPATH):
$ export GOPATH=/opt/local/golang-oz
$ sudo mkdir -p $GOPATH
$ sudo chown user. $GOPATH
  1. To build Oz with the required external Golang dependencies, run the following commands:

Firstly we build the godep tool:

$ go get

Now checkout the source using either:

$ git clone src/

Or alternatively if we want to create a development environment use:

$ go get -d

We are ready to build and install:

$ sudo apt-get install libacl1-dev
$ cd $GOPATH/src/
$ $GOPATH/bin/godep go install ./...
$ sudo cp $GOPATH/bin/oz* /usr/local/bin
$ sudo mkdir -p /var/lib/oz/cells.d
$ sudo cp $GOPATH/src/* /var/lib/oz/cells.d/
$ sudo mkdir /etc/oz
$ sudo cp $GOPATH/src/ /etc/oz/blacklist-generic.seccomp
$ sudo cp $GOPATH/src/* /etc/network/if-up.d/
$ sudo chmod a+x /etc/network/if-up.d/oz
$ sudo cp $GOPATH/src/* /etc/network/if-post-down.d/
$ sudo cp $GOPATH/src/ /lib/systemd/system/oz-daemon.service
$ sudo cp $GOPATH/src/ /etc/NetworkManager/conf.d/oz.conf
$ sudo dpkg-divert --add --package oz --rename --divert /etc/xpra/xpra.conf.pkg-dist /etc/xpra/xpra.conf
$ sudo cp $GOPATH/src/ /etc/xpra/xpra.conf
$ sudo systemctl enable oz-daemon.service

Enabling a profile

Once installed you can enable profiles using the

command as such (using the profile for the 'evince' application):
$ sudo oz-setup install evince

This will install a symlink to the oz client executable in place of the original, the original executable will be moved to

. This behavior can be altered using the divertpath and divertsuffix configuration flags.

Disabling a profile

If you want to disable a profile that you're not using or prior to uninstalling Oz, you can run the following command (once again with 'evince' as the target application):

$ sudo oz-setup remove evince

If you have already uninstalled Oz you can remove the divertions manually using the


Viewing the status of a profile

You can view the status of a profile using the

$ sudo oz-setup status /usr/bin/lowriter
Package divert is installed for:     /usr/bin/libreoffice
Package divert is installed for:     /usr/bin/lowriter
Package divert is installed for:     /usr/bin/lobase
Package divert is installed for:     /usr/bin/localc
Package divert is installed for:     /usr/bin/loffice
<...output truncated for clarity>


Firstly you must launch the daemon utility either with the init script or manually:

$ sudo oz-daemon

Once the daemon is started you can transparently launch any applications for which you have enabled the profile. This means Oz sandboxing will be used whether you launch your browser from gnome-shell or from the command line.

Any files inside of your home passed as arguments to the command (either via double clicking or program arguments) are automatically added to the whitelist (if the profile supports


The OZ gnome-shell extension allows you to easily interface running sandboxes: to add/remove files inside a sandbox, open a shell inside a sandbox, and terminate a sandbox.

If you wish to run an executable outside of the sandbox simply call it at

, for example:
$ /usr/bin-oz/evince.unsafe

Advanced Usage Information

Oz client commands


executable acts as a client for the daemon when called directly. It provides a number of commands to interact with sandboxes.
  • profiles
    : lists available profiles
  • launch 
    : launches a sandbox for the given profile name, pass the
    flag to prevent execution of the default program
  • list
    : lists the running sandboxes
  • kill 
    : kills the sandbox with the given numerical id
  • kill all
    : kills all running sandboxes
  • shell 
    : enters a shell in a given sandbox, mostly useful for debugging
  • logs [-f]
    : prints out the logs, pass
    to follow the output

Oz-daemon configurations

In nearly every case the default configurations should be used, but for debugging and development purposes some flags are configurable inside of the

file. You can view the current configuration by running the following command:
$ oz-setup config show

Config file : /etc/oz/oz.conf ################################################################## profile_dir : /var/lib/oz/cells.d # Directory containing the sandbox profiles shell_path : /bin/bash # Path of the shell used when entering a sandbox prefix_path : /usr/local # Prefix path containing the oz executables etc_prefix : /etc/oz # Prefix for configuration files sandbox_path : /srv/oz # Path of the sandboxes base bridge_mac : 6A:A8:2E:56:E8:9C # MAC Address of the bridge interface divert_suffix : unsafe # Suffix using for dpkg-divert of application executables, can be left empty when using a divert path divert_path : true # Whether the diverted executable should be moved out of the path nm_ignore_file : /etc/NetworkManager/conf.d/oz.conf # Path to the NetworkManager ignore config file, disables the warning if empty use_full_dev : false # Give sandboxes full access to devices instead of a restricted set allow_root_shell: false # Allow entering a sandbox shell as root log_xpra : false # Log output of Xpra environment_vars: [USER USERNAME LOGNAME LANG LANGUAGE _ TZ=UTC] # Default environment variables passed to sandboxes default_groups : [audio video] # List of default group names that can be used inside the sandbox


Profiles files are simple JSON files located, by default, in

. They must include at minimum the path to the executable to be sandboxed using the
key. It may also define more executables to run under the same sandbox under the
array; in which case a
key must also be specified. Some other base options are also available:
  • path
    : if multiple executables are to be sandboxed under the same profile
  • allow_files
    : whether to allow binding of files passed as arguments inside the sandbox (does not affect files added manually)
  • auto_shutdown
    : whether the sandbox should be terminated right away after the process exits, one of [yes|no], (defaults to
  • watchdog
    : an array of strings containing the names of process the auto-shutdown feature should look for in case the main process spawns a detached process.
  • allowed_groups
    : an array of user groups assigned to the user inside the sandbox
  • default_params
    : an array of default params to pass to the program whenever it is executed


This section defines the configuration of the Xserver (namely xpra). Possible options are:

  • enabled
    : whether or not to use the Xserver
  • enable_tray
    : whether or not to enable the Xpra tray diagnostic menu/tray (This requires the
    Top Icons
    gnome-shell extension!)
  • tray_icon
    : the path to an icon file to use for the to tray menu
  • window_icon
    : the path to an icon file to use for windows
  • audio_mode
    : one of [none|pulseaudio~~|speaker|full~~] selects the audio passthrough mode (defaults: none) (Only pulseaudio mode supported at this time)
  • disable_clipboard
    : optionally disable clipboard sharing
  • enable_notifications
    : enable passing of dbus notifications

Network configs

The network can be configured in one of three different ways: host, bridge, and empty namespace, as defined in the

  • empty
    : the sandbox will live with an empty network namespace (ie: only
  • bridge
    : the sandbox will have its own network namespace and use veth to join a bridge named
  • none
    : don't even configure the loopback interface, connection proxy will be unavailable
  • host
    : the sandbox will share the network namespace with the host (usually not desirable)

Port Forwarding config

Oz allows you to forward ports on the loopback interface between the host and the sandbox. This is useful so that you can expose some services (such as a socks proxy) to the sandbox without giving the sandbox any real network access. You may define as many forwards, called

in the configuration, as you like. Each socket configuration contains the following keys:
  • type
    : One of
    , or
    , this defines whether to connect (client) or listen (server) on the host side
  • proto
    : One of
    , or
    , or
  • port
    : The network port number to connect to
  • destination
    : Optional, in client mode this is the address to connect to, in server mode this is the address to bind to. Defaults to localhost.

Bind list

There exists two types of bindlists: a whitelist and a blacklist. The whitelist allows you to bring files from the host into the sandbox; while the blacklist allows you to remove access to specific files or directories.


key specifies the path of the directory or file to bind.

Both of these types support a few ways of resolving files:

  • In the path by using the
  • In the home by using the
  • By replacing
    with the user numeric id.
  • By replacing
    with the user login.
  • By replacing any
    with the current localized version of that XDG directory.
  • By path globbing using the

The whitelist carries some extra properties:

  • An optional
    key can be specified to bind the file to a different path inside the sandbox.
  • If the original file does not exist and is inside the home, an empty directory will be created in its place if the
    key is set.
  • If the target already exists the whitelist will fail to bind unless the
    key is set.
  • A profile will fail to launch if a whitelist item is missing unless the
    key is set.
  • An item can be marked as read only with the
    boolean key.
  • Files passed as arguments to the command while launching are automatically added to the whitelist (if the
    boolean key is set).

The whitelist carries some extra caveats:

  • If the original file is a symlink it is resolved, but the target remains the same.


One can specify which environment variables to pass by defining them in this list. It is also possible to define static variables by also defining a

attribute in the list item.


Oz supports both whitelist and blacklist seccomp policies for sandboxed applications. Seccomp allows for See the Oz Seccomp documentation page for more details.

Oz can also run sandboxed applications with whitelist and blacklist seccomp policies loaded, but in non-enforced (audit only) mode. More information is available on the Oz seccomp non-enforcement mode documentation page.


You can find a list of existing profiles in the repository. Here is the porfile for running the

"path": "/usr/bin/torbrowser-launcher"
, "watchdog": ["start-tor-browser", "firefox"]
, "xserver": {
    "enabled": true
    , "enable_tray": false
    , "tray_icon":"/usr/share/pixmaps/torbrowser80.xpm"
    , "audio_mode": "pulseaudio"
, "networking":{
    , "sockets": [
        {"type":"client", "proto":"tcp", "port":9050}
        , {"type":"client", "proto":"tcp", "port":9051}
, "whitelist": [
    {"path":"${HOME}/.local/share/torbrowser", "can_create":true}
    , {"path":"${HOME}/.config/torbrowser", "can_create":true}
    , {"path":"${HOME}/Downloads/TorBrowser", "can_create":true}
    , {"path":"/run/tor/control.authcookie", "ignore":true}
, "blacklist": [
, "environment": [
    , {"name":"TOR_SOCKS_HOST"}
    , {"name":"TOR_SOCKS_PORT"}
    , {"name":"TOR_CONTROL_PORT"}
    , {"name":"TOR_CONTROL_PASSWD"}
, "allowed_groups": ["debian-tor"]
, "seccomp": {
    , "enforce": true


Q: Why don't you use unprivileged user namespaces, I hear it would be far more secure!

A: Please see this issue which explains the reasoning and tracks multiple unprivileged user namespace related kernel vulnerabilities

Obsidian Zebra

We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.