1
* Choose the Client Network Interface
3
You MUST make sure that the correct network interface is specified
4
in the DEVICE setting in the "/etc/initramfs-tools/initramfs.conf"
5
file. *If* this is changed, it will be necessary to update the
6
initrd image by running the command
8
update-initramfs -k all -u
10
The device can be overridden at boot time on the Linux kernel
11
command line using the sixth colon-separated field of the "ip="
12
option; for exact syntax, read the documentation in the file
13
"/usr/share/doc/linux-doc-*/Documentation/filesystems/nfsroot.txt",
14
available in the "linux-doc-*" package.
16
Note that since this network interface is used in the initial RAM
17
disk environment, the network interface *must* exist at that stage.
18
Thus, the interface can *not* be a pseudo-interface such as "br0" or
19
"tun0"; instead, a real interface (such as "eth0") must be used.
1
21
* Adding a Client Password to the Server
3
23
The server must be given a password to give back to the client on
16
36
is possible to verify that the correct password will be received by
17
37
this client by running the command, on the 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 \
39
/usr/lib/mandos/plugins.d/mandos-client \
23
40
--pubkey=/etc/keys/mandos/pubkey.txt \
24
41
--seckey=/etc/keys/mandos/seckey.txt; echo
27
44
it, and output it to standard output. There it can be verified to
28
45
be the correct password, before rebooting.
32
If it ever should be necessary, the Mandos client can be temporarily
33
prevented from running at startup by passing the parameter
34
"mandos=off" to the kernel.
36
* Specifying a Client Network Interface
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
46
update-initramfs -k all -u
48
The device can also be overridden at boot time on the Linux kernel
49
command line using the sixth colon-separated field of the "ip="
50
option; for exact syntax, read the documentation in the file
51
"/usr/share/doc/linux-doc-*/Documentation/filesystems/nfs/nfsroot.txt",
52
available in the "linux-doc-*" package.
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
60
"/etc/mandos/network-hooks.d", from where it will be copied into the
61
initial RAM disk. Example network hook scripts can be found in
62
"/usr/share/doc/mandos-client/examples/network-hooks.d".
64
47
* User-Supplied Plugins
66
49
Any plugins found in "/etc/mandos/plugins.d" will override and add
77
60
Mandos client will be the new default way for getting a password for
78
61
the root file system when booting.
65
If it ever should be necessary, the Mandos client can be temporarily
66
prevented from running at startup by passing the parameter
67
"mandos=off" to the kernel.
80
69
* Non-local Connection (Not Using ZeroConf)
82
71
If the "ip=" kernel command line option is used to specify a
83
72
complete IP address and device name, as noted above, it then becomes
84
73
possible to specify a specific IP address and port to connect to,
85
74
instead of using ZeroConf. The syntax for doing this is
86
"mandos=connect:<IP_ADDRESS>:<PORT_NUMBER>" on the kernel command
75
"mandos=connect:<IP_ADDRESS>:<PORT_NUMBER>".
77
Warning: this will cause the client to make exactly one attempt at
78
connecting, and then fail if it does not succeed.
89
80
For very advanced users, it it possible to specify simply
90
81
"mandos=connect" on the kernel command line to make the system only
93
84
work, "--options-for=mandos-client:--connect=<ADDRESS>:<PORT>" needs
94
85
to be manually added to the file "/etc/mandos/plugin-runner.conf".
96
-- Teddy Hogeborn <teddy@recompile.se>, Mon, 29 Jun 2015 18:17:41 +0200
87
-- Teddy Hogeborn <teddy@fukt.bsnet.se>, Tue, 8 Sep 2009 08:25:58 +0200
added
removed
debian/mandos-client.README.Debian
