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/$(dpkg-architecture -qDEB_HOST_MULTIARCH \
20
)/mandos/plugins.d/mandos-client \
19
/usr/lib/mandos/plugins.d/mandos-client \
21
20
--pubkey=/etc/keys/mandos/pubkey.txt \
22
21
--seckey=/etc/keys/mandos/seckey.txt; echo
34
33
* Specifying a Client Network Interface
36
At boot time the network interfaces to use will by default be
37
automatically detected. If this should result in incorrect
38
interfaces, edit the DEVICE setting in the
39
"/etc/initramfs-tools/initramfs.conf" file. (The default setting is
40
empty, meaning it will autodetect the interface.) *If* the DEVICE
41
setting is changed, it will be necessary to update the initrd image
42
by running the 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
44
42
update-initramfs -k all -u
46
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
47
45
command line using the sixth colon-separated field of the "ip="
48
46
option; for exact syntax, read the documentation in the file
49
"/usr/share/doc/linux-doc-*/Documentation/filesystems/nfs/nfsroot.txt",
47
"/usr/share/doc/linux-doc-*/Documentation/filesystems/nfsroot.txt",
50
48
available in the "linux-doc-*" package.
52
Note that since the network interfaces are used in the initial RAM
53
disk environment, the network interfaces *must* exist at that stage.
54
Thus, an interface can *not* be a pseudo-interface such as "br0" or
55
"tun0"; instead, only real interfaces (such as "eth0") can be used.
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.
56
54
This can be overcome by writing a "network hook" program to create
57
an interface (see mandos-client(8mandos)) and placing it in
55
the interface (see mandos-client(8mandos)) and placing it in
58
56
"/etc/mandos/network-hooks.d", from where it will be copied into the
59
57
initial RAM disk. Example network hook scripts can be found in
60
"/usr/share/doc/mandos-client/examples/network-hooks.d".
58
"/usr/share/doc/mandos-client/network-hooks.d".
62
60
* User-Supplied Plugins
91
89
work, "--options-for=mandos-client:--connect=<ADDRESS>:<PORT>" needs
92
90
to be manually added to the file "/etc/mandos/plugin-runner.conf".
94
-- Teddy Hogeborn <teddy@recompile.se>, Mon, 28 Oct 2013 11:02:26 +0100
92
-- Teddy Hogeborn <teddy@fukt.bsnet.se>, Sun, 27 Nov 2011 15:06:34 +0100
added
removed
debian/mandos-client.README.Debian
