20
16
is possible to verify that the correct password will be received by
21
17
this client by running the command, on the client:
23
MANDOSPLUGINHELPERDIR=/usr/lib/$(dpkg-architecture \
24
-qDEB_HOST_MULTIARCH)/mandos/plugin-helpers \
25
/usr/lib/$(dpkg-architecture -qDEB_HOST_MULTIARCH \
26
)/mandos/plugins.d/mandos-client \
19
/usr/lib/mandos/plugins.d/mandos-client \
27
20
--pubkey=/etc/keys/mandos/pubkey.txt \
28
--seckey=/etc/keys/mandos/seckey.txt \
29
--tls-privkey=/etc/keys/mandos/tls-privkey.pem \
30
--tls-pubkey=/etc/keys/mandos/tls-pubkey.pem; echo
21
--seckey=/etc/keys/mandos/seckey.txt; echo
32
23
This command should retrieve the password from the server, decrypt
33
24
it, and output it to standard output. There it can be verified to
42
33
* Specifying a Client Network Interface
44
At boot time the network interfaces to use will by default be
45
automatically detected. If this should result in incorrect
46
interfaces, edit the DEVICE setting in the
35
At boot time the network interface to use will by default be
36
automatically detected. If this should result in an incorrect
37
interface, edit the DEVICE setting in the
47
38
"/etc/initramfs-tools/initramfs.conf" file. (The default setting is
48
empty, meaning it will autodetect the interfaces.) *If* the DEVICE
39
empty, meaning it will autodetect the interface.) *If* the DEVICE
49
40
setting is changed, it will be necessary to update the initrd image
50
by running this command:
41
by running the command
52
(For initramfs-tools:)
53
43
update-initramfs -k all -u
56
dpkg-reconfigure dracut
58
The device can also be overridden at boot time on the Linux kernel
45
The device can be overridden at boot time on the Linux kernel
59
46
command line using the sixth colon-separated field of the "ip="
60
47
option; for exact syntax, read the documentation in the file
61
"/usr/share/doc/linux-doc-*/Documentation/filesystems/nfs/nfsroot.txt",
48
"/usr/share/doc/linux-doc-*/Documentation/filesystems/nfsroot.txt",
62
49
available in the "linux-doc-*" package.
64
Note that since the network interfaces are used in the initial RAM
65
disk environment, the network interfaces *must* exist at that stage.
66
Thus, an interface can *not* be a pseudo-interface such as "br0" or
67
"tun0"; instead, only real interfaces (such as "enp1s0" or "eth0")
68
can be used. This can be overcome by writing a "network hook"
69
program to create an interface (see mandos-client(8mandos)) and
70
placing it in "/etc/mandos/network-hooks.d", from where it will be
71
copied into the initial RAM disk. Example network hook scripts can
72
be found in "/usr/share/doc/mandos-client/examples/network-hooks.d".
51
Note that since this network interface is used in the initial RAM
52
disk environment, the network interface *must* exist at that stage.
53
Thus, the interface can *not* be a pseudo-interface such as "br0" or
54
"tun0"; instead, only real interface (such as "eth0") can be used.
55
This can be overcome by writing a "network hook" program to create
56
the 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".
74
61
* User-Supplied Plugins
76
63
Any plugins found in "/etc/mandos/plugins.d" will override and add
77
64
to the normal Mandos plugins. When adding or changing plugins, do
78
not forget to update the initial RAM disk image:
65
not forget to update the initital RAM disk image:
80
(For initramfs-tools:)
81
67
update-initramfs -k all -u
84
dpkg-reconfigure dracut
86
69
* Do *NOT* Edit "/etc/crypttab"
100
83
"mandos=connect:<IP_ADDRESS>:<PORT_NUMBER>" on the kernel command
103
For very advanced users, it is possible to specify "mandos=connect"
104
on the kernel command line to make the system only set up the
105
network (using the data in the "ip=" option) and not pass any extra
106
"--connect" options to mandos-client at boot. For this to work,
107
"--options-for=mandos-client:--connect=<ADDRESS>:<PORT>" needs to be
108
manually added to the file "/etc/mandos/plugin-runner.conf" or, if
109
dracut is used with systemd, the "--connect=<ADDRESS>:<PORT>"
110
options needs to be added to an environment variable in an override
111
file for the "ask-password-mandos" service, as detailed in the file
112
"/usr/lib/dracut/modules.d/90mandos/ask-password-mandos.service".
114
* Diffie-Hellman Parameters
116
On installation, a file with Diffie-Hellman parameters,
117
/etc/keys/mandos/dhparams.pem, will be generated and automatically
118
installed into the initial RAM disk image and also used by the
119
Mandos Client on boot. If different parameters are needed for
120
policy or other reasons, simply replace the existing dhparams.pem
121
file and update the initial RAM disk image.
123
-- Teddy Hogeborn <teddy@recompile.se>, Sun, 8 Sep 2024 02:09:20 +0200
86
For very advanced users, it it possible to specify simply
87
"mandos=connect" on the kernel command line to make the system only
88
set up the network (using the data in the "ip=" option) and not pass
89
any extra "--connect" options to mandos-client at boot. For this to
90
work, "--options-for=mandos-client:--connect=<ADDRESS>:<PORT>" needs
91
to be manually added to the file "/etc/mandos/plugin-runner.conf".
93
-- Teddy Hogeborn <teddy@recompile.se>, Fri, 1 Jun 2012 23:46:13 +0200
added
removed
debian/mandos-client.README.Debian
