8
8
* Use the Correct Network Interface
10
If some other network interface than "eth0" is used, it will be
11
necessary to edit /etc/mandos/plugin-runner.conf to uncomment and
12
change the line there. If this is done, it will be necessary to
13
update the initrd image by doing "update-initramfs -k all -u".
10
Make sure that the correct network interface is specified in the
11
DEVICE setting in the "/etc/initramfs-tools/initramfs.conf" file.
12
If this is changed, it will be necessary to update the initrd image
13
by doing "update-initramfs -k all -u". This setting can be
14
overridden at boot time on the Linux kernel command line using the
15
sixth colon-separated field of the "ip=" option; for exact syntax,
16
see the file "Documentation/nfsroot.txt" in the Linux source tree.
18
Note that since this is used in the initial RAM disk environment,
19
the network interface must exist at that stage. Thus, the interface
20
can *not* be a pseudo-interface such as "br0" or "tun0"; instead, a
21
real interface (such as "eth0") must be used.
23
31
--seckey=/etc/keys/mandos/seckey.txt; echo
25
33
This command should retrieve the password from the server, decrypt
26
it, and output it to standard output. It is now possible to verify
27
the correctness of the password before rebooting.
34
it, and output it to standard output. There it can be verified to
35
be the correct password, before rebooting.
29
37
* User-Supplied Plugins
31
39
Any plugins found in /etc/mandos/plugins.d will override and add to
32
40
the normal Mandos plugins. When adding or changing plugins, do not
33
41
forget to update the initital RAM disk image:
35
43
# update-initramfs -k all -u
37
45
* Do *NOT* Edit /etc/crypttab
39
47
It is NOT necessary to edit /etc/crypttab to specify
40
48
/usr/lib/mandos/plugin-runner as a keyscript for the root file
41
49
system; if no keyscript is given for the root file system, the
42
50
Mandos client will be the new default way for getting a password for
43
51
the root file system when booting.
45
-- Teddy Hogeborn <teddy@fukt.bsnet.se>, Sun, 5 Oct 2008 19:04:26 +0200
55
If it ever should be necessary, the Mandos client can be temporarily
56
prevented from running at startup by passing the parameter
57
"mandos=off" to the kernel.
59
* Non-local Connection (Not Using ZeroConf)
61
If the "ip=" kernel command line option is used to specify a
62
complete IP address and device name, as noted above, it then becomes
63
possible to specify a specific IP address and port to connect to,
64
instead of using ZeroConf. The syntax for doing this is
65
"mandos=connect:<IP_ADDRESS>:<PORT_NUMBER>".
67
Warning: this will cause the client to make exactly one attempt at
68
connecting, and then fail if it does not succeed.
70
For very advanced users, it it possible to specify simply
71
"mandos=connect" on the kernel command line to make the system only
72
set up the network (using the data in the "ip=" option) and not pass
73
any extra "--connect" options to mandos-client at boot. For this to
74
work, "--options-for=mandos-client:--connect=<ADDRESS>:<PORT>" needs
75
to be manually added to the file "/etc/mandos/plugin-runner.conf".
77
-- Teddy Hogeborn <teddy@fukt.bsnet.se>, Tue, 14 Apr 2009 16:51:18 +0200
added
removed
debian/mandos-client.README.Debian
