16
20
is possible to verify that the correct password will be received by
17
21
this client by running the command, on the client:
19
/usr/lib/mandos/plugins.d/mandos-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 \
20
27
--pubkey=/etc/keys/mandos/pubkey.txt \
21
--seckey=/etc/keys/mandos/seckey.txt; echo
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
23
32
This command should retrieve the password from the server, decrypt
24
33
it, and output it to standard output. There it can be verified to
33
42
* Specifying a Client Network Interface
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
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
38
47
"/etc/initramfs-tools/initramfs.conf" file. (The default setting is
39
empty, meaning it will autodetect the interface.) *If* the DEVICE
48
empty, meaning it will autodetect the interfaces.) *If* the DEVICE
40
49
setting is changed, it will be necessary to update the initrd image
41
by running the command
50
by running this command:
52
(For initramfs-tools:)
43
53
update-initramfs -k all -u
56
dpkg-reconfigure dracut
45
The device can be overridden at boot time on the Linux kernel
58
The device can also be overridden at boot time on the Linux kernel
46
59
command line using the sixth colon-separated field of the "ip="
47
60
option; for exact syntax, read the documentation in the file
48
"/usr/share/doc/linux-doc-*/Documentation/filesystems/nfsroot.txt",
61
"/usr/share/doc/linux-doc-*/Documentation/filesystems/nfs/nfsroot.txt",
49
62
available in the "linux-doc-*" package.
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/network-hooks.d".
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".
61
74
* User-Supplied Plugins
83
100
"mandos=connect:<IP_ADDRESS>:<PORT_NUMBER>" on the kernel command
86
For very advanced users, it it possible to specify simply
103
For very advanced users, it is possible to specify simply
87
104
"mandos=connect" on the kernel command line to make the system only
88
105
set up the network (using the data in the "ip=" option) and not pass
89
106
any extra "--connect" options to mandos-client at boot. For this to
90
107
work, "--options-for=mandos-client:--connect=<ADDRESS>:<PORT>" needs
91
108
to be manually added to the file "/etc/mandos/plugin-runner.conf".
93
-- Teddy Hogeborn <teddy@recompile.se>, Mon, 28 Nov 2011 23:07:22 +0100
110
* Diffie-Hellman Parameters
112
On installation, a file with Diffie-Hellman parameters,
113
/etc/keys/mandos/dhparams.pem, will be generated and automatically
114
installed into the initital RAM disk image and also used by the
115
Mandos Client on boot. If different parameters are needed for
116
policy or other reasons, simply replace the existing dhparams.pem
117
file and update the initital RAM disk image.
119
-- Teddy Hogeborn <teddy@recompile.se>, Mon, 15 Jul 2019 16:47:02 +0200