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
47
"/etc/initramfs-tools/initramfs.conf" file. (The default setting is
48
empty, meaning it will autodetect the interfaces.) *If* the DEVICE
49
setting is changed, it will be necessary to update the initrd image
50
by running this command:
35
At boot time the network interface to use will by default be
36
automatically detected. If should result in an incorrect interface,
37
edit the DEVICE setting in the "/etc/initramfs-tools/initramfs.conf"
38
file. (The default setting is empty, meaning to autodetect the
39
interface.) *If* the DEVICE setting is changed, it will be
40
necessary to update the initrd image by running the command
52
(For initramfs-tools:)
53
42
update-initramfs -k all -u
56
dpkg-reconfigure dracut
58
The device can also be overridden at boot time on the Linux kernel
44
The device can be overridden at boot time on the Linux kernel
59
45
command line using the sixth colon-separated field of the "ip="
60
46
option; for exact syntax, read the documentation in the file
61
"/usr/share/doc/linux-doc-*/Documentation/filesystems/nfs/nfsroot.txt",
47
"/usr/share/doc/linux-doc-*/Documentation/filesystems/nfsroot.txt",
62
48
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".
50
Note that since this network interface is used in the initial RAM
51
disk environment, the network interface *must* exist at that stage.
52
Thus, the interface can *not* be a pseudo-interface such as "br0" or
53
"tun0"; instead, only real interface (such as "eth0") can be used.
54
This can be overcome by writing a "network hook" program to create
55
the interface (see mandos-client(8mandos)) and placing it in
56
"/etc/mandos/network-hooks.d", from where it will be copied into the
57
initial RAM disk. Example network hook scripts can be found in
58
"/usr/share/doc/mandos-client/network-hooks.d".
74
60
* User-Supplied Plugins
100
82
"mandos=connect:<IP_ADDRESS>:<PORT_NUMBER>" on the kernel command
103
For very advanced users, it is possible to specify simply
85
For very advanced users, it it possible to specify simply
104
86
"mandos=connect" on the kernel command line to make the system only
105
87
set up the network (using the data in the "ip=" option) and not pass
106
88
any extra "--connect" options to mandos-client at boot. For this to
107
89
work, "--options-for=mandos-client:--connect=<ADDRESS>:<PORT>" needs
108
90
to be manually added to the file "/etc/mandos/plugin-runner.conf".
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
92
-- Teddy Hogeborn <teddy@recompile.se>, Mon, 28 Nov 2011 23:07:22 +0100