7
7
Debian 5.0 "lenny" or Ubuntu 8.04 "Hardy Heron".
9
This is mostly for scripts to make sure that the client is
10
installed and started in the initial RAM disk environment and that
11
the initrd.img file is automatically made unreadable. The programs
12
themselves *could* be run in other distributions, but they *are*
13
specific to GNU/Linux systems, and not intended to be portable to
9
This is mostly for the support scripts which make sure that the
10
client is installed and started in the initial RAM disk environment
11
and that the initrd.img file is automatically made unreadable. The
12
server and client programs themselves *could* be run in other
13
distributions, but they *are* specific to GNU/Linux systems, and
14
are not intended to be portable to other Unixes.
65
70
2. On the computer to run as a Mandos server, run the following
66
command: "sudo make install-server".
68
(This creates a configuration without any clients configured; we
72
For Debian: su -c 'make install-server'
73
For Ubuntu: sudo make install-server
75
(This creates a configuration without any clients configured; you
69
76
need an actually configured client to do that; see below.)
71
78
* Installing the Mandos client.
73
80
1. Do "make all doc".
75
82
2. On the computer to run as a Mandos client, run the following
76
command: "sudo make install-client". This will also create an
77
OpenPGP key, which will take some time and entropy, so either
78
wait patiently or frob your mouse until it's done.
80
3. Run "mandos-keygen --password". When prompted, enter the
81
password/passphrase for the encrypted root file system on this
82
client computer. It will output a section of text, starting with
83
a [section header]. Copy and paste this into the file
84
"/etc/mandos/clients.conf" *on the server computer*.
86
4. On the server computer, start the server by running the command
87
"invoke-rc.d mandos start".
84
For Debian: su -c 'make install-client'
85
For Ubuntu: sudo make install-client
87
This will also create an OpenPGP key, which will take some time
88
and entropy, so be patient.
90
3. Run the following command:
91
For Debian: su -c 'mandos-keygen --password'
92
For Ubuntu: sudo mandos-keygen --password
94
When prompted, enter the password/passphrase for the encrypted
95
root file system on this client computer. The command will
96
output a section of text, starting with a [section header]. Copy
97
and append this to the file "/etc/mandos/clients.conf" *on the
100
4. Configure the client to use the correct network interface. The
101
default is "eth0", and if this needs to be adjusted, it will be
102
necessary to edit /etc/mandos/plugin-runner.conf to uncomment and
103
change the line there. If that file is changed, the initrd.img
104
file must be updated, possibly using the following command:
106
# update-initramfs -k all -u
108
5. On the server computer, start the server by running the command
109
For Debian: su -c 'invoke-rc.d mandos start'
110
For Ubuntu: sudo invoke-rc.d mandos start
112
At this point, it is possible to verify that the correct password
113
will be received by the client by running the command:
115
# /usr/lib/mandos/plugins.d/mandos-client \
116
--pubkey=/etc/keys/mandos/pubkey.txt \
117
--seckey=/etc/keys/mandos/seckey.txt; echo
119
This command should retrieve the password from the server,
120
decrypt it, and output it to standard output.
122
After this, the client computer should be able to reboot without
123
needing a password entered on the console, as long as it does not
124
take more than an hour to reboot.
89
126
* Further customizations
91
128
You may want to tighten or loosen the timeouts in the server
92
129
configuration files; see mandos.conf(5) and mandos-clients.conf(5).
93
Is IPsec is not used, it is suggested that a more cryptographically
130
If IPsec is not used, it is suggested that a more cryptographically
94
131
secure checker program is used and configured, since without IPsec
95
132
ping packets can be faked.