97
97
and append this to the file "/etc/mandos/clients.conf" *on the
100
4. On the server computer, start the server by running the command
100
4. Configure the client to use the correct network interface. The
101
default is "eth0", and if this needs to be adjusted, it will be
102
necessary to edit /etc/mandos/plugin-runner.conf to uncomment and
103
change the line there. If that file is changed, the initrd.img
104
file must be updated, possibly using the following command:
106
# update-initramfs -k all -u
108
5. On the server computer, start the server by running the command
101
109
For Debian: su -c 'invoke-rc.d mandos start'
102
110
For Ubuntu: sudo invoke-rc.d mandos start
112
At this point, it is possible to verify that the correct password
113
will be received by the client by running the command:
115
# /usr/lib/mandos/plugins.d/mandos-client \
116
--pubkey=/etc/keys/mandos/pubkey.txt \
117
--seckey=/etc/keys/mandos/seckey.txt; echo
119
This command should retrieve the password from the server,
120
decrypt it, and output it to standard output.
104
122
After this, the client computer should be able to reboot without
105
123
needing a password entered on the console, as long as it does not
106
124
take more than an hour to reboot.
110
128
You may want to tighten or loosen the timeouts in the server
111
129
configuration files; see mandos.conf(5) and mandos-clients.conf(5).
112
Is IPsec is not used, it is suggested that a more cryptographically
130
If IPsec is not used, it is suggested that a more cryptographically
113
131
secure checker program is used and configured, since without IPsec
114
132
ping packets can be faked.
added
removed
INSTALL
