54
54
<command>&COMMANDNAME;</command>
56
56
<arg choice="plain"><option>--connect
57
<replaceable>IPADDR</replaceable><literal>:</literal
57
<replaceable>ADDRESS</replaceable><literal>:</literal
58
58
><replaceable>PORT</replaceable></option></arg>
59
59
<arg choice="plain"><option>-c
60
<replaceable>IPADDR</replaceable><literal>:</literal
60
<replaceable>ADDRESS</replaceable><literal>:</literal
61
61
><replaceable>PORT</replaceable></option></arg>
65
<arg choice="plain"><option>--keydir
66
<replaceable>DIRECTORY</replaceable></option></arg>
67
<arg choice="plain"><option>-d
68
<replaceable>DIRECTORY</replaceable></option></arg>
72
65
<arg choice="plain"><option>--interface
73
66
<replaceable>NAME</replaceable></option></arg>
74
67
<arg choice="plain"><option>-i
128
121
communicates with <citerefentry><refentrytitle
129
122
>mandos</refentrytitle><manvolnum>8</manvolnum></citerefentry>
130
123
to get a password. It uses IPv6 link-local addresses to get
131
network connectivity, Zeroconf to find the server, and TLS with
132
an OpenPGP key to ensure authenticity and confidentiality. It
124
network connectivity, Zeroconf to find servers, and TLS with an
125
OpenPGP key to ensure authenticity and confidentiality. It
133
126
keeps running, trying all servers on the network, until it
134
receives a satisfactory reply.
127
receives a satisfactory reply or a TERM signal is received.
137
130
This program is not meant to be run directly; it is really meant
138
131
to run as a plugin of the <application>Mandos</application>
139
132
<citerefentry><refentrytitle>plugin-runner</refentrytitle>
140
<manvolnum>8mandos</manvolnum></citerefentry>, which in turn
141
runs as a <quote>keyscript</quote> specified in the
142
<citerefentry><refentrytitle>crypttab</refentrytitle>
143
<manvolnum>5</manvolnum></citerefentry> file.
133
<manvolnum>8mandos</manvolnum></citerefentry>, which runs in the
134
initial <acronym>RAM</acronym> disk environment because it is
135
specified as a <quote>keyscript</quote> in the <citerefentry>
136
<refentrytitle>crypttab</refentrytitle><manvolnum>5</manvolnum>
137
</citerefentry> file.
300
<refsect1 id="overview">
301
<title>OVERVIEW</title>
302
<xi:include href="../overview.xml"/>
304
This program is the client part. It is a plugin started by
305
<citerefentry><refentrytitle>plugin-runner</refentrytitle>
306
<manvolnum>8mandos</manvolnum></citerefentry> which will run in
307
an initial <acronym>RAM</acronym> disk environment.
310
This program could, theoretically, be used as a keyscript in
311
<filename>/etc/crypttab</filename>, but it would then be
312
impossible to enter a password for the encrypted root disk at
313
the console, since this program does not read from the console
314
at all. This is why a separate plugin (<citerefentry>
315
<refentrytitle>password-prompt</refentrytitle>
316
<manvolnum>8mandos</manvolnum></citerefentry>) does that, which
317
will be run in parallel to this one by the plugin runner.
336
321
<refsect1 id="exit_status">
337
322
<title>EXIT STATUS</title>
341
326
successfully decrypted and output on standard output. The
342
327
program will exit with a non-zero exit status only if a critical
343
328
error occurs. Otherwise, it will forever connect to new
344
<application>Mandosservers</application> servers as they appear,
345
trying to get a decryptable password.
349
<!-- <refsect1 id="environment"> -->
350
<!-- <title>ENVIRONMENT</title> -->
329
<application>Mandos</application> servers as they appear, trying
330
to get a decryptable password.
334
<refsect1 id="environment">
335
<title>ENVIRONMENT</title>
337
This program does not use any environment variables, not even
338
the ones provided by <citerefentry><refentrytitle
339
>cryptsetup</refentrytitle><manvolnum>8</manvolnum>
348
<term><filename>/conf/conf.d/mandos/pubkey.txt</filename
350
<term><filename>/conf/conf.d/mandos/seckey.txt</filename
354
OpenPGP public and private key files, in <quote>ASCII
355
Armor</quote> format. These are the default file names,
356
they can be changed with the <option>--pubkey</option> and
357
<option>--seckey</option> options.
364
<!-- <refsect1 id="bugs"> -->
365
<!-- <title>BUGS</title> -->
352
<!-- This program does not use any environment variables. -->
354
368
<!-- </refsect1> -->
368
370
<refsect1 id="example">
369
371
<title>EXAMPLE</title>
373
Note that normally, command line options will not be given
374
directly, but via options for the Mandos <citerefentry
375
><refentrytitle>plugin-runner</refentrytitle>
376
<manvolnum>8mandos</manvolnum></citerefentry>.
380
Normal invocation needs no options, if the network interface
381
is <quote>eth0</quote>:
384
<userinput>&COMMANDNAME;</userinput>
389
Search for Mandos servers on another interface:
392
<!-- do not wrap this line -->
393
<userinput>&COMMANDNAME; --interface eth1</userinput>
398
Run in debug mode, and use a custom key:
402
<!-- do not wrap this line -->
403
<userinput>&COMMANDNAME; --debug --pubkey keydir/pubkey.txt --seckey keydir/seckey.txt</userinput>
409
Run in debug mode, with a custom key, and do not use Zeroconf
410
to locate a server; connect directly to the IPv6 address
411
<quote><systemitem class="ipaddress"
412
>2001:db8:f983:bd0b:30de:ae4a:71f2:f672</systemitem></quote>,
413
port 4711, using interface eth2:
417
<!-- do not wrap this line -->
418
<userinput>&COMMANDNAME; --debug --pubkey keydir/pubkey.txt --seckey keydir/seckey.txt --connect 2001:db8:f983:bd0b:30de:ae4a:71f2:f672:4711 --interface eth2</userinput>
374
424
<refsect1 id="security">
375
425
<title>SECURITY</title>
427
This program is set-uid to root, but will switch back to the
428
original (and presumably non-privileged) user and group after
429
bringing up the network interface.
432
To use this program for its intended purpose (see <xref
433
linkend="purpose"/>), the password for the root file system will
434
have to be given out to be stored in a server computer, after
435
having been encrypted using an OpenPGP key. This encrypted data
436
which will be stored in a server can only be decrypted by the
437
OpenPGP key, and the data will only be given out to those
438
clients who can prove they actually have that key. This key,
439
however, is stored unencrypted on the client side in its initial
440
<acronym>RAM</acronym> disk image file system. This is normally
441
readable by all, but this is normally fixed during installation
442
of this program; file permissions are set so that no-one is able
446
The only remaining weak point is that someone with physical
447
access to the client hard drive might turn off the client
448
computer, read the OpenPGP keys directly from the hard drive,
449
and communicate with the server. The defense against this is
450
that the server is supposed to notice the client disappearing
451
and will stop giving out the encrypted data. Therefore, it is
452
important to set the timeout and checker interval values tightly
453
on the server. See <citerefentry><refentrytitle
454
>mandos</refentrytitle><manvolnum>8</manvolnum></citerefentry>.
457
It will also help if the checker program on the server is
458
configured to request something from the client which can not be
459
spoofed by someone else on the network, unlike unencrypted
460
<acronym>ICMP</acronym> echo (<quote>ping</quote>) replies.
463
<emphasis>Note</emphasis>: This makes it completely insecure to
464
have <application >Mandos</application> clients which dual-boot
465
to another operating system which is <emphasis>not</emphasis>
466
trusted to keep the initial <acronym>RAM</acronym> disk image
380
471
<refsect1 id="see_also">
381
472
<title>SEE ALSO</title>
474
<citerefentry><refentrytitle>cryptsetup</refentrytitle>
475
<manvolnum>8</manvolnum></citerefentry>,
476
<citerefentry><refentrytitle>crypttab</refentrytitle>
477
<manvolnum>5</manvolnum></citerefentry>,
383
478
<citerefentry><refentrytitle>mandos</refentrytitle>
384
479
<manvolnum>8</manvolnum></citerefentry>,
385
480
<citerefentry><refentrytitle>password-prompt</refentrytitle>
387
482
<citerefentry><refentrytitle>plugin-runner</refentrytitle>
388
483
<manvolnum>8mandos</manvolnum></citerefentry>
392
<ulink url="http://www.zeroconf.org/">Zeroconf</ulink>
396
<ulink url="http://www.avahi.org/">Avahi</ulink>
401
url="http://www.gnu.org/software/gnutls/">GnuTLS</ulink>
406
url="http://www.gnupg.org/related_software/gpgme/">
411
<citation>RFC 4880: <citetitle>OpenPGP Message
412
Format</citetitle></citation>
416
<citation>RFC 5081: <citetitle>Using OpenPGP Keys for
417
Transport Layer Security</citetitle></citation>
421
<citation>RFC 4291: <citetitle>IP Version 6 Addressing
422
Architecture</citetitle>, section 2.5.6, Link-Local IPv6
423
Unicast Addresses</citation>
488
<ulink url="http://www.zeroconf.org/">Zeroconf</ulink>
492
Zeroconf is the network protocol standard used for finding
493
Mandos servers on the local network.
499
<ulink url="http://www.avahi.org/">Avahi</ulink>
503
Avahi is the library this program calls to find Zeroconf
510
<ulink url="http://www.gnu.org/software/gnutls/"
515
GnuTLS is the library this client uses to implement TLS for
516
communicating securely with the server, and at the same time
517
send the public OpenPGP key to the server.
523
<ulink url="http://www.gnupg.org/related_software/gpgme/"
528
GPGME is the library used to decrypt the OpenPGP data sent
535
RFC 4291: <citetitle>IP Version 6 Addressing
536
Architecture</citetitle>
541
<term>Section 2.2: <citetitle>Text Representation of
542
Addresses</citetitle></term>
543
<listitem><para/></listitem>
546
<term>Section 2.5.5.2: <citetitle>IPv4-Mapped IPv6
547
Address</citetitle></term>
548
<listitem><para/></listitem>
551
<term>Section 2.5.6, <citetitle>Link-Local IPv6 Unicast
552
Addresses</citetitle></term>
555
This client uses IPv6 link-local addresses, which are
556
immediately usable since a link-local addresses is
557
automatically assigned to a network interfaces when it
567
RFC 4346: <citetitle>The Transport Layer Security (TLS)
568
Protocol Version 1.1</citetitle>
572
TLS 1.1 is the protocol implemented by GnuTLS.
578
RFC 4880: <citetitle>OpenPGP Message Format</citetitle>
582
The data received from the server is binary encrypted
589
RFC 5081: <citetitle>Using OpenPGP Keys for Transport Layer
594
This is implemented by GnuTLS and used by this program so
595
that OpenPGP keys can be used.