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
* Choose the Client Network Interface
3
You MUST make sure that the correct network interface is specified
4
in the DEVICE setting in the "/etc/initramfs-tools/initramfs.conf"
5
file. *If* this is changed, it will be necessary to update the
6
initrd image by running the command
8
update-initramfs -k all -u
10
The device can be overridden at boot time on the Linux kernel
11
command line using the sixth colon-separated field of the "ip="
12
option; for exact syntax, read the documentation in the file
13
"/usr/share/doc/linux-doc-*/Documentation/filesystems/nfsroot.txt",
14
available in the "linux-doc-*" package.
16
Note that since this network interface is used in the initial RAM
17
disk environment, the network interface *must* exist at that stage.
18
Thus, the interface can *not* be a pseudo-interface such as "br0" or
19
"tun0"; instead, a real interface (such as "eth0") must be used.
21
* Adding a Client Password to the Server
23
The server must be given a password to give back to the client on
24
boot time. This password must be a one which can be used to unlock
25
the root file system device. On the *client*, run this command:
27
mandos-keygen --password
29
It will prompt for a password and output a config file section.
30
This output should be copied to the Mandos server and added to the
31
file "/etc/mandos/clients.conf" there.
33
* Testing that it Works (Without Rebooting)
35
After the server has been started with this client's key added, it
36
is possible to verify that the correct password will be received by
22
37
this client by running the command, on the client:
24
# /usr/lib/mandos/plugins.d/mandos-client \
39
/usr/lib/mandos/plugins.d/mandos-client \
25
40
--pubkey=/etc/keys/mandos/pubkey.txt \
26
41
--seckey=/etc/keys/mandos/seckey.txt; echo
32
47
* 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:
49
Any plugins found in "/etc/mandos/plugins.d" will override and add
50
to the normal Mandos plugins. When adding or changing plugins, do
51
not forget to update the initital RAM disk image:
38
# update-initramfs -k all -u
53
update-initramfs -k all -u
40
* Do *NOT* Edit /etc/crypttab
55
* 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
57
It is NOT necessary to edit "/etc/crypttab" to specify
58
"/usr/lib/mandos/plugin-runner" as a keyscript for the root file
44
59
system; if no keyscript is given for the root file system, the
45
60
Mandos client will be the new default way for getting a password for
46
61
the root file system when booting.
added
removed
debian/mandos-client.README.Debian
