diff options
author | Kali Kaneko (leap communications) <kali@leap.se> | 2017-05-31 18:08:24 +0200 |
---|---|---|
committer | Kali Kaneko (leap communications) <kali@leap.se> | 2017-05-31 18:53:47 +0200 |
commit | 5388eb01e016a7d109dc53c464df94b412300e0c (patch) | |
tree | c4b91d357dc0d6f7b3fd591ae64bf3057cdef2f8 | |
parent | 72d93a61cf9aff5996952d55e56981eb5a22d989 (diff) |
[docs] document helper installation
-rw-r--r-- | docs/hacking/index.rst | 24 |
1 files changed, 24 insertions, 0 deletions
diff --git a/docs/hacking/index.rst b/docs/hacking/index.rst index 489e257..62a1186 100644 --- a/docs/hacking/index.rst +++ b/docs/hacking/index.rst @@ -116,6 +116,30 @@ Debugging Bitmask A must-read for debugging the Bitmask Core daemon is the :ref:`manhole HowTo <manhole>`. +Bitmask privileged runner +---------------------------------- + +For launching VPN and the firewall, Bitmask needs to run with administrative +privileges. In linux, ``bitmask_root`` is the component that runs with root +privileges. We currently depend on ``pkexec`` and ``polkit`` to execute it as +root. In order to do that, Bitmask needs to put some policykit helper files in a +place that is root-writeable. + +If you have installed Bitmask from some distro package, these folders should be +already in place. If you're running the Bitmask bundles, the first time you will +be prompted to authenticate to allow these helpers to be copied over (or any +time that these helpers change). + +However, if you're running bitmask in a headless environment, you will want to +copy the helpers manually, without involving pkexec. To do that, use:: + + sudo `which bitmask_helpers` install + +You can also uninstall them:: + + sudo `which bitmask_helpers` uninstall + + How to contribute code --------------------------------- |