1
1
<?xml version="1.0" encoding="UTF-8"?>
2
2
<!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
3
3
"http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
4
<!ENTITY VERSION "1.0">
4
5
<!ENTITY COMMANDNAME "mandos-client">
5
<!ENTITY TIMESTAMP "2011-08-08">
6
<!ENTITY % common SYSTEM "../common.ent">
6
<!ENTITY TIMESTAMP "2008-09-06">
10
9
<refentry xmlns:xi="http://www.w3.org/2001/XInclude">
12
11
<title>Mandos Manual</title>
13
<!-- NWalsh’s docbook scripts use this to generate the footer: -->
12
<!-- Nwalsh’s docbook scripts use this to generate the footer: -->
14
13
<productname>Mandos</productname>
15
<productnumber>&version;</productnumber>
14
<productnumber>&VERSION;</productnumber>
16
15
<date>&TIMESTAMP;</date>
37
34
<holder>Teddy Hogeborn</holder>
38
35
<holder>Björn Påhlsson</holder>
40
37
<xi:include href="../legalnotice.xml"/>
44
41
<refentrytitle>&COMMANDNAME;</refentrytitle>
45
42
<manvolnum>8mandos</manvolnum>
126
115
</refsynopsisdiv>
128
117
<refsect1 id="description">
129
118
<title>DESCRIPTION</title>
131
120
<command>&COMMANDNAME;</command> is a client program that
132
121
communicates with <citerefentry><refentrytitle
133
122
>mandos</refentrytitle><manvolnum>8</manvolnum></citerefentry>
134
to get a password. In slightly more detail, this client program
135
brings up a network interface, uses the interface’s IPv6
136
link-local address to get network connectivity, uses Zeroconf to
137
find servers on the local network, and communicates with servers
138
using TLS with an OpenPGP key to ensure authenticity and
139
confidentiality. This client program keeps running, trying all
140
servers on the network, until it receives a satisfactory reply
141
or a TERM signal. After all servers have been tried, all
142
servers are periodically retried. If no servers are found it
143
will wait indefinitely for new servers to appear.
123
to get a password. It uses IPv6 link-local addresses to get
124
network connectivity, Zeroconf to find servers, and TLS with an
125
OpenPGP key to ensure authenticity and confidentiality. It
126
keeps running, trying all servers on the network, until it
127
receives a satisfactory reply or a TERM signal is received.
146
130
This program is not meant to be run directly; it is really meant
203
<term><option>--interface=<replaceable
204
>NAME</replaceable></option></term>
187
<term><option>--interface=
188
<replaceable>NAME</replaceable></option></term>
206
190
<replaceable>NAME</replaceable></option></term>
209
193
Network interface that will be brought up and scanned for
210
Mandos servers to connect to. The default is the empty
211
string, which will automatically choose an appropriate
194
Mandos servers to connect to. The default it
195
<quote><literal>eth0</literal></quote>.
215
198
If the <option>--connect</option> option is used, this
216
199
specifies the interface to use to connect to the address
220
Note that since this program will normally run in the
221
initial RAM disk environment, the interface must be an
222
interface which exists at that stage. Thus, the interface
223
can not be a pseudo-interface such as <quote>br0</quote>
224
or <quote>tun0</quote>; such interfaces will not exist
225
until much later in the boot process, and can not be used
229
<replaceable>NAME</replaceable> can be the string
230
<quote><literal>none</literal></quote>; this will not use
231
any specific interface, and will not bring up an interface
232
on startup. This is not recommended, and only meant for
287
<term><option>--delay=<replaceable
288
>SECONDS</replaceable></option></term>
291
After bringing the network interface up, the program waits
292
for the interface to arrive in a <quote>running</quote>
293
state before proceeding. During this time, the kernel log
294
level will be lowered to reduce clutter on the system
295
console, alleviating any other plugins which might be
296
using the system console. This option sets the upper
297
limit of seconds to wait. The default is 2.5 seconds.
303
<term><option>--retry=<replaceable
304
>SECONDS</replaceable></option></term>
307
All Mandos servers are tried repeatedly until a password
308
is received. This value specifies, in seconds, how long
309
between each successive try <emphasis>for the same
310
server</emphasis>. The default is 10 seconds.
316
254
<term><option>--debug</option></term>
389
327
server could be found and the password received from it could be
390
328
successfully decrypted and output on standard output. The
391
329
program will exit with a non-zero exit status only if a critical
392
error occurs. Otherwise, it will forever connect to any
393
discovered <application>Mandos</application> servers, trying to
394
get a decryptable password and print it.
330
error occurs. Otherwise, it will forever connect to new
331
<application>Mandos</application> servers as they appear, trying
332
to get a decryptable password and print it.
472
410
<informalexample>
474
412
Run in debug mode, with a custom key, and do not use Zeroconf
475
to locate a server; connect directly to the IPv6 link-local
476
address <quote><systemitem class="ipaddress"
477
>fe80::aede:48ff:fe71:f6f2</systemitem></quote>, port 4711,
478
using interface eth2:
413
to locate a server; connect directly to the IPv6 address
414
<quote><systemitem class="ipaddress"
415
>2001:db8:f983:bd0b:30de:ae4a:71f2:f672</systemitem></quote>,
416
port 4711, using interface eth2:
482
420
<!-- do not wrap this line -->
483
<userinput>&COMMANDNAME; --debug --pubkey keydir/pubkey.txt --seckey keydir/seckey.txt --connect fe80::aede:48ff:fe71:f6f2:4711 --interface eth2</userinput>
421
<userinput>&COMMANDNAME; --debug --pubkey keydir/pubkey.txt --seckey keydir/seckey.txt --connect 2001:db8:f983:bd0b:30de:ae4a:71f2:f672:4711 --interface eth2</userinput>
486
424
</informalexample>
489
427
<refsect1 id="security">
490
428
<title>SECURITY</title>
511
449
The only remaining weak point is that someone with physical
512
450
access to the client hard drive might turn off the client
513
451
computer, read the OpenPGP keys directly from the hard drive,
514
and communicate with the server. To safeguard against this, the
515
server is supposed to notice the client disappearing and stop
516
giving out the encrypted data. Therefore, it is important to
517
set the timeout and checker interval values tightly on the
518
server. See <citerefentry><refentrytitle
452
and communicate with the server. The defense against this is
453
that the server is supposed to notice the client disappearing
454
and will stop giving out the encrypted data. Therefore, it is
455
important to set the timeout and checker interval values tightly
456
on the server. See <citerefentry><refentrytitle
519
457
>mandos</refentrytitle><manvolnum>8</manvolnum></citerefentry>.
536
474
<refsect1 id="see_also">
537
475
<title>SEE ALSO</title>
539
<citerefentry><refentrytitle>intro</refentrytitle>
540
<manvolnum>8mandos</manvolnum></citerefentry>,
541
477
<citerefentry><refentrytitle>cryptsetup</refentrytitle>
542
478
<manvolnum>8</manvolnum></citerefentry>,
543
479
<citerefentry><refentrytitle>crypttab</refentrytitle>
added
removed
plugins.d/mandos-client.xml
