3
A client key has been automatically created in /etc/keys/mandos.
4
The next step is to run "mandos-keygen --password" to get a config
5
file section. This should be appended to /etc/mandos/clients.conf
8
* Use the Correct Network Interface
10
Make sure that the correct network interface is specified in the
11
DEVICE setting in the "/etc/initramfs-tools/initramfs.conf" file.
12
If this is changed, it will be necessary to update the initrd image
13
by doing "update-initramfs -k all -u". This setting can be
14
overridden at boot time on the Linux kernel command line using the
15
sixth colon-separated field of the "ip=" option; for exact syntax,
16
see the file "Documentation/nfsroot.txt" in the Linux source tree.
20
After the server has been started and this client's key added, it is
21
possible to verify that the correct password will be received by
1
* Adding a Client Password to the Server
3
The server must be given a password to give back to the client on
4
boot time. This password must be a one which can be used to unlock
5
the root file system device. On the *client*, run this command:
7
mandos-keygen --password
9
It will prompt for a password and output a config file section.
10
This output should be copied to the Mandos server and added to the
11
file "/etc/mandos/clients.conf" there.
13
* Testing that it Works (Without Rebooting)
15
After the server has been started with this client's key added, it
16
is possible to verify that the correct password will be received by
22
17
this client by running the command, on the client:
24
# /usr/lib/mandos/plugins.d/mandos-client \
19
/usr/lib/mandos/plugins.d/mandos-client \
25
20
--pubkey=/etc/keys/mandos/pubkey.txt \
26
21
--seckey=/etc/keys/mandos/seckey.txt; echo
29
24
it, and output it to standard output. There it can be verified to
30
25
be the correct password, before rebooting.
29
If it ever should be necessary, the Mandos client can be temporarily
30
prevented from running at startup by passing the parameter
31
"mandos=off" to the kernel.
33
* Specifying a Client Network Interface
35
At boot time the network interfaces to use will by default be
36
automatically detected. If this should result in incorrect
37
interfaces, edit the DEVICE setting in the
38
"/etc/initramfs-tools/initramfs.conf" file. (The default setting is
39
empty, meaning it will autodetect the interface.) *If* the DEVICE
40
setting is changed, it will be necessary to update the initrd image
41
by running the command
43
update-initramfs -k all -u
45
The device can also be overridden at boot time on the Linux kernel
46
command line using the sixth colon-separated field of the "ip="
47
option; for exact syntax, read the documentation in the file
48
"/usr/share/doc/linux-doc-*/Documentation/filesystems/nfsroot.txt",
49
available in the "linux-doc-*" package.
51
Note that since the network interfaces are used in the initial RAM
52
disk environment, the network interfaces *must* exist at that stage.
53
Thus, an interface can *not* be a pseudo-interface such as "br0" or
54
"tun0"; instead, only real interfaces (such as "eth0") can be used.
55
This can be overcome by writing a "network hook" program to create
56
an interface (see mandos-client(8mandos)) and placing it in
57
"/etc/mandos/network-hooks.d", from where it will be copied into the
58
initial RAM disk. Example network hook scripts can be found in
59
"/usr/share/doc/mandos-client/examples/network-hooks.d".
32
61
* User-Supplied Plugins
34
Any plugins found in /etc/mandos/plugins.d will override and add to
35
the normal Mandos plugins. When adding or changing plugins, do not
36
forget to update the initital RAM disk image:
63
Any plugins found in "/etc/mandos/plugins.d" will override and add
64
to the normal Mandos plugins. When adding or changing plugins, do
65
not forget to update the initital RAM disk image:
38
# update-initramfs -k all -u
67
update-initramfs -k all -u
40
* Do *NOT* Edit /etc/crypttab
69
* Do *NOT* Edit "/etc/crypttab"
42
It is NOT necessary to edit /etc/crypttab to specify
43
/usr/lib/mandos/plugin-runner as a keyscript for the root file
71
It is NOT necessary to edit "/etc/crypttab" to specify
72
"/usr/lib/mandos/plugin-runner" as a keyscript for the root file
44
73
system; if no keyscript is given for the root file system, the
45
74
Mandos client will be the new default way for getting a password for
46
75
the root file system when booting.
50
If it ever should be necessary, the Mandos client can be temporarily
51
prevented from running at startup by passing the parameter
52
"mandos=off" to the kernel.
54
77
* Non-local Connection (Not Using ZeroConf)
56
79
If the "ip=" kernel command line option is used to specify a
57
80
complete IP address and device name, as noted above, it then becomes
58
81
possible to specify a specific IP address and port to connect to,
59
82
instead of using ZeroConf. The syntax for doing this is
60
"mandos=connect:<IP_ADDRESS>:<PORT_NUMBER>".
62
Warning: this will cause the client to make exactly one attempt at
63
connecting, and then fail if it does not succeed.
83
"mandos=connect:<IP_ADDRESS>:<PORT_NUMBER>" on the kernel command
65
86
For very advanced users, it it possible to specify simply
66
87
"mandos=connect" on the kernel command line to make the system only
added
removed
debian/mandos-client.README.Debian
