1
This file documents the next steps to take after installation of the
2
Debian package, and also contain some notes specific to the Debian
3
packaging which are not also in the manual.
5
1
* Adding a Client Password to the Server
7
3
The server must be given a password to give back to the client on
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
21
--seckey=/etc/keys/mandos/seckey.txt; echo
40
33
* Specifying a Client Network Interface
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
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
45
38
"/etc/initramfs-tools/initramfs.conf" file. (The default setting is
46
39
empty, meaning it will autodetect the interface.) *If* the DEVICE
47
40
setting is changed, it will be necessary to update the initrd image
50
43
update-initramfs -k all -u
52
The device can also be overridden at boot time on the Linux kernel
45
The device can be overridden at boot time on the Linux kernel
53
46
command line using the sixth colon-separated field of the "ip="
54
47
option; for exact syntax, read the documentation in the file
55
"/usr/share/doc/linux-doc-*/Documentation/filesystems/nfs/nfsroot.txt",
48
"/usr/share/doc/linux-doc-*/Documentation/filesystems/nfsroot.txt",
56
49
available in the "linux-doc-*" package.
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.
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.
62
55
This can be overcome by writing a "network hook" program to create
63
an interface (see mandos-client(8mandos)) and placing it in
56
the interface (see mandos-client(8mandos)) and placing it in
64
57
"/etc/mandos/network-hooks.d", from where it will be copied into the
65
58
initial RAM disk. Example network hook scripts can be found in
66
"/usr/share/doc/mandos-client/examples/network-hooks.d".
59
"/usr/share/doc/mandos-client/network-hooks.d".
68
61
* User-Supplied Plugins
97
90
work, "--options-for=mandos-client:--connect=<ADDRESS>:<PORT>" needs
98
91
to be manually added to the file "/etc/mandos/plugin-runner.conf".
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>, Sun, 12 Jul 2015 03:24:24 +0200
93
-- Teddy Hogeborn <teddy@recompile.se>, Mon, 28 Nov 2011 23:07:22 +0100
added
removed
debian/mandos-client.README.Debian
