16
16
is possible to verify that the correct password will be received by
17
17
this client by running the command, on the client:
19
/usr/lib/mandos/plugins.d/mandos-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 \
20
23
--pubkey=/etc/keys/mandos/pubkey.txt \
21
24
--seckey=/etc/keys/mandos/seckey.txt; echo
33
36
* Specifying a Client Network Interface
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
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
42
46
update-initramfs -k all -u
44
The device can be overridden at boot time on the Linux kernel
48
The device can also be overridden at boot time on the Linux kernel
45
49
command line using the sixth colon-separated field of the "ip="
46
50
option; for exact syntax, read the documentation in the file
47
"/usr/share/doc/linux-doc-*/Documentation/filesystems/nfsroot.txt",
51
"/usr/share/doc/linux-doc-*/Documentation/filesystems/nfs/nfsroot.txt",
48
52
available in the "linux-doc-*" package.
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 (see
55
mandos-client(8mandos)) and placing it in
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
56
60
"/etc/mandos/network-hooks.d", from where it will be copied into the
57
initial RAM disk. Some example network hook scripts can be found in
58
"/usr/share/doc/mandos-client/network-hooks.d".
61
initial RAM disk. Example network hook scripts can be found in
62
"/usr/share/doc/mandos-client/examples/network-hooks.d".
60
64
* User-Supplied Plugins
89
93
work, "--options-for=mandos-client:--connect=<ADDRESS>:<PORT>" needs
90
94
to be manually added to the file "/etc/mandos/plugin-runner.conf".
92
-- Teddy Hogeborn <teddy@recompile.se>, Sun, 27 Nov 2011 03:30:40 +0100
96
-- Teddy Hogeborn <teddy@recompile.se>, Mon, 29 Jun 2015 18:17:41 +0200