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
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
If some other network interface than "eth0" is used, it will be
11
necessary to edit /etc/mandos/plugin-runner.conf to uncomment and
12
change the line there. If this is done, it will be necessary to
13
update the initrd image by doing "update-initramfs -k all -u".
17
After the server has been started and this client's key added, it is
18
possible to verify that the correct password will be received by
17
19
this client by running the command, on the client:
19
MANDOSPLUGINHELPERDIR=/usr/lib/$(dpkg-architecture \
20
-qDEB_HOST_MULTIARCH)/mandos/plugin-helpers \
21
/usr/lib/$(dpkg-architecture -qDEB_HOST_MULTIARCH \
22
)/mandos/plugins.d/mandos-client \
21
# /usr/lib/mandos/plugins.d/mandos-client \
23
22
--pubkey=/etc/keys/mandos/pubkey.txt \
24
23
--seckey=/etc/keys/mandos/seckey.txt; echo
26
25
This command should retrieve the password from the server, decrypt
27
it, and output it to standard output. There it can be verified to
28
be the correct password, before rebooting.
26
it, and output it to standard output. It is now possible to verify
27
the correctness of the password before rebooting.
29
* User-Supplied Plugins
31
Any plugins found in /etc/mandos/plugins.d will override and add to
32
the normal Mandos plugins. When adding or changing plugins, do not
33
forget to update the initital RAM disk image:
35
# update-initramfs -k all -u
37
* Do *NOT* Edit /etc/crypttab
39
It is NOT necessary to edit /etc/crypttab to specify
40
/usr/lib/mandos/plugin-runner as a keyscript for the root file
41
system; if no keyscript is given for the root file system, the
42
Mandos client will be the new default way for getting a password for
43
the root file system when booting.
33
48
prevented from running at startup by passing the parameter
34
49
"mandos=off" to the kernel.
36
* Specifying a Client Network Interface
38
At boot time the network interfaces to use will by default be
39
automatically detected. If this should result in incorrect
40
interfaces, edit the DEVICE setting in the
41
"/etc/initramfs-tools/initramfs.conf" file. (The default setting is
42
empty, meaning it will autodetect the interface.) *If* the DEVICE
43
setting is changed, it will be necessary to update the initrd image
44
by running the command
46
update-initramfs -k all -u
48
The device can also be overridden at boot time on the Linux kernel
49
command line using the sixth colon-separated field of the "ip="
50
option; for exact syntax, read the documentation in the file
51
"/usr/share/doc/linux-doc-*/Documentation/filesystems/nfs/nfsroot.txt",
52
available in the "linux-doc-*" package.
54
Note that since the network interfaces are used in the initial RAM
55
disk environment, the network interfaces *must* exist at that stage.
56
Thus, an interface can *not* be a pseudo-interface such as "br0" or
57
"tun0"; instead, only real interfaces (such as "eth0") can be used.
58
This can be overcome by writing a "network hook" program to create
59
an interface (see mandos-client(8mandos)) and placing it in
60
"/etc/mandos/network-hooks.d", from where it will be copied into the
61
initial RAM disk. Example network hook scripts can be found in
62
"/usr/share/doc/mandos-client/examples/network-hooks.d".
64
* User-Supplied Plugins
66
Any plugins found in "/etc/mandos/plugins.d" will override and add
67
to the normal Mandos plugins. When adding or changing plugins, do
68
not forget to update the initital RAM disk image:
70
update-initramfs -k all -u
72
* Do *NOT* Edit "/etc/crypttab"
74
It is NOT necessary to edit "/etc/crypttab" to specify
75
"/usr/lib/mandos/plugin-runner" as a keyscript for the root file
76
system; if no keyscript is given for the root file system, the
77
Mandos client will be the new default way for getting a password for
78
the root file system when booting.
80
* Non-local Connection (Not Using ZeroConf)
82
If the "ip=" kernel command line option is used to specify a
83
complete IP address and device name, as noted above, it then becomes
84
possible to specify a specific IP address and port to connect to,
85
instead of using ZeroConf. The syntax for doing this is
86
"mandos=connect:<IP_ADDRESS>:<PORT_NUMBER>" on the kernel command
89
For very advanced users, it it possible to specify simply
90
"mandos=connect" on the kernel command line to make the system only
91
set up the network (using the data in the "ip=" option) and not pass
92
any extra "--connect" options to mandos-client at boot. For this to
93
work, "--options-for=mandos-client:--connect=<ADDRESS>:<PORT>" needs
94
to be manually added to the file "/etc/mandos/plugin-runner.conf".
96
-- Teddy Hogeborn <teddy@recompile.se>, Mon, 29 Jun 2015 18:17:41 +0200
51
-- Teddy Hogeborn <teddy@fukt.bsnet.se>, Mon, 12 Jan 2009 02:29:10 +0100
added
removed
debian/mandos-client.README.Debian
