Skip to content

Latest commit

 

History

History
143 lines (107 loc) · 5.23 KB

INSTALL

File metadata and controls

143 lines (107 loc) · 5.23 KB

-*- org -*-

Prerequisites

Operating System

Debian 8.0 “jessie” or Ubuntu 15.10 “Wily Werewolf” (or later).

This is mostly for the support scripts which make sure that the client is installed and started in the initial RAM disk environment and that the initial RAM file system image file is automatically made unreadable. The server and client programs themselves could be run in other distributions, but they are specific to GNU/Linux systems, and are not written with portabillity to other Unixes in mind.

Libraries

The following libraries and packages are needed. (It is possible that it might work with older versions of some of these, but these versions are confirmed to work. Newer versions are almost certainly OK.)

Documentation

These are required to build the manual pages for both the server and client:

Package names: docbook docbook-xsl

To build just the documentation, run the command “make doc”. Then the manual page “mandos.8”, for example, can be read by running “man -l mandos.8”.

Mandos Server

Strongly recommended:

Package names: avahi-daemon python python-dbus python-gi python-urwid pkg-config fping ssh-client

Mandos Client

Strongly recommended:

Package names: initramfs-tools libgnutls-dev libavahi-core-dev gnupg libgpgme11-dev pkg-config ssh

Installing the Mandos server

  1. Do “make doc”.
  2. On the computer to run as a Mandos server, run the following command: For Debian: su -c ‘make install-server’ For Ubuntu: sudo make install-server

    (This creates a configuration without any clients configured; you need an actually configured client to do that; see below.)

Installing the Mandos client.

  1. Do “make all doc”.
  2. On the computer to run as a Mandos client, run the following command: For Debian: su -c ‘make install-client’ For Ubuntu: sudo make install-client

    This will also create an OpenPGP key, which will take some time and entropy, so be patient.

  3. Run the following command: For Debian: su -c ‘mandos-keygen –password’ For Ubuntu: sudo mandos-keygen –password

    When prompted, enter the password/passphrase for the encrypted root file system on this client computer. The command will output a section of text, starting with a [section header]. Copy and append this to the file “/etc/mandos/clients.conf” on the server computer.

  4. Configure the client to use any special configuration needed for your local system. Note: This is not necessary if the server is present on the same wired local network as the client. If you do make changes to /etc/mandos/plugin-runner.conf, the initrd.img file must be updated, possibly using the following command:
  1. On the server computer, start the server by running the command For Debian: su -c ‘invoke-rc.d mandos start’ For Ubuntu: sudo service mandos start

    At this point, it is possible to verify that the correct password will be received by the client by running the command:

–pubkey=/etc/keys/mandos/pubkey.txt \ –seckey=/etc/keys/mandos/seckey.txt; echo

This command should retrieve the password from the server, decrypt it, and output it to standard output.

After this, the client computer should be able to reboot without needing a password entered on the console, as long as it does not take more than five minutes to reboot.

Further customizations

You may want to tighten or loosen the timeouts in the server configuration files; see mandos.conf(5) and mandos-clients.conf(5). If IPsec is not used and SSH is not installed, it is suggested that a more cryptographically secure checker program is used and configured, since, without IPsec, ping packets can be faked.