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
28
--seckey=/etc/keys/mandos/seckey.txt; echo
33
40
* 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
42
At boot time the network interfaces to use will by default be
43
automatically detected. If this should result in incorrect
44
interfaces, edit the DEVICE setting in the
45
"/etc/initramfs-tools/initramfs.conf" file. (The default setting is
46
empty, meaning it will autodetect the interfaces.) *If* the DEVICE
47
setting is changed, it will be necessary to update the initrd image
48
by running this command:
42
50
update-initramfs -k all -u
44
The device can be overridden at boot time on the Linux kernel
52
The device can also be overridden at boot time on the Linux kernel
45
53
command line using the sixth colon-separated field of the "ip="
46
54
option; for exact syntax, read the documentation in the file
47
"/usr/share/doc/linux-doc-*/Documentation/filesystems/nfsroot.txt",
55
"/usr/share/doc/linux-doc-*/Documentation/filesystems/nfs/nfsroot.txt",
48
56
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.
58
Note that since the network interfaces are used in the initial RAM
59
disk environment, the network interfaces *must* exist at that stage.
60
Thus, an interface can *not* be a pseudo-interface such as "br0" or
61
"tun0"; instead, only real interfaces (such as "eth0") can be used.
54
62
This can be overcome by writing a "network hook" program to create
55
the interface (see mandos-client(8mandos)) and placing it in
63
an interface (see mandos-client(8mandos)) and placing it in
56
64
"/etc/mandos/network-hooks.d", from where it will be copied into the
57
65
initial RAM disk. Example network hook scripts can be found in
58
"/usr/share/doc/mandos-client/network-hooks.d".
66
"/usr/share/doc/mandos-client/examples/network-hooks.d".
60
68
* User-Supplied Plugins
82
90
"mandos=connect:<IP_ADDRESS>:<PORT_NUMBER>" on the kernel command
85
For very advanced users, it it possible to specify simply
93
For very advanced users, it is possible to specify simply
86
94
"mandos=connect" on the kernel command line to make the system only
87
95
set up the network (using the data in the "ip=" option) and not pass
88
96
any extra "--connect" options to mandos-client at boot. For this to
89
97
work, "--options-for=mandos-client:--connect=<ADDRESS>:<PORT>" needs
90
98
to be manually added to the file "/etc/mandos/plugin-runner.conf".
92
-- Teddy Hogeborn <teddy@fukt.bsnet.se>, Sun, 27 Nov 2011 15:06:34 +0100
100
* Diffie-Hellman Parameters
102
On installation, a file with Diffie-Hellman parameters,
103
/etc/keys/mandos/dhparams.pem, will be generated and automatically
104
installed into the initital RAM disk image and also used by the
105
Mandos Client on boot. If different parameters are needed for
106
policy or other reasons, simply replace the existing dhparams.pem
107
file and update the initital RAM disk image.
109
-- Teddy Hogeborn <teddy@recompile.se>, Tue, 21 Jun 2016 21:43:49 +0200
added
removed
debian/mandos-client.README.Debian
