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">
5
<!ENTITY COMMANDNAME "password-request">
6
<!ENTITY TIMESTAMP "2008-09-03">
4
<!ENTITY COMMANDNAME "mandos-client">
5
<!ENTITY TIMESTAMP "2009-01-24">
6
<!ENTITY % common SYSTEM "../common.ent">
9
10
<refentry xmlns:xi="http://www.w3.org/2001/XInclude">
11
12
<title>Mandos Manual</title>
12
<!-- Nwalsh’s docbook scripts use this to generate the footer: -->
13
<!-- NWalsh’s docbook scripts use this to generate the footer: -->
13
14
<productname>Mandos</productname>
14
<productnumber>&VERSION;</productnumber>
15
<productnumber>&version;</productnumber>
15
16
<date>&TIMESTAMP;</date>
46
48
<refname><command>&COMMANDNAME;</command></refname>
50
Client for <application>Mandos</application>
54
56
<command>&COMMANDNAME;</command>
56
58
<arg choice="plain"><option>--connect
57
<replaceable>IPADDR</replaceable><literal>:</literal
59
<replaceable>ADDRESS</replaceable><literal>:</literal
58
60
><replaceable>PORT</replaceable></option></arg>
59
61
<arg choice="plain"><option>-c
60
<replaceable>IPADDR</replaceable><literal>:</literal
62
<replaceable>ADDRESS</replaceable><literal>:</literal
61
63
><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
67
<arg choice="plain"><option>--interface
73
68
<replaceable>NAME</replaceable></option></arg>
74
69
<arg choice="plain"><option>-i
122
121
</refsynopsisdiv>
124
123
<refsect1 id="description">
125
124
<title>DESCRIPTION</title>
127
126
<command>&COMMANDNAME;</command> is a client program that
128
127
communicates with <citerefentry><refentrytitle
129
128
>mandos</refentrytitle><manvolnum>8</manvolnum></citerefentry>
130
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
133
keeps running, trying all servers on the network, until it
134
receives a satisfactory reply.
129
to get a password. In slightly more detail, this client program
130
brings up a network interface, uses the interface’s IPv6
131
link-local address to get network connectivity, uses Zeroconf to
132
find servers on the local network, and communicates with servers
133
using TLS with an OpenPGP key to ensure authenticity and
134
confidentiality. This client program keeps running, trying all
135
servers on the network, until it receives a satisfactory reply
136
or a TERM signal is received. If no servers are found, or after
137
all servers have been tried, it waits indefinitely for new
137
141
This program is not meant to be run directly; it is really meant
382
<refsect1 id="files">
363
383
<title>FILES</title>
386
<term><filename>/conf/conf.d/mandos/pubkey.txt</filename
388
<term><filename>/conf/conf.d/mandos/seckey.txt</filename
392
OpenPGP public and private key files, in <quote>ASCII
393
Armor</quote> format. These are the default file names,
394
they can be changed with the <option>--pubkey</option> and
395
<option>--seckey</option> options.
402
<!-- <refsect1 id="bugs"> -->
403
<!-- <title>BUGS</title> -->
374
408
<refsect1 id="example">
375
409
<title>EXAMPLE</title>
411
Note that normally, command line options will not be given
412
directly, but via options for the Mandos <citerefentry
413
><refentrytitle>plugin-runner</refentrytitle>
414
<manvolnum>8mandos</manvolnum></citerefentry>.
418
Normal invocation needs no options, if the network interface
419
is <quote>eth0</quote>:
422
<userinput>&COMMANDNAME;</userinput>
427
Search for Mandos servers (and connect to them) using another
431
<!-- do not wrap this line -->
432
<userinput>&COMMANDNAME; --interface eth1</userinput>
437
Run in debug mode, and use a custom key:
441
<!-- do not wrap this line -->
442
<userinput>&COMMANDNAME; --debug --pubkey keydir/pubkey.txt --seckey keydir/seckey.txt</userinput>
448
Run in debug mode, with a custom key, and do not use Zeroconf
449
to locate a server; connect directly to the IPv6 address
450
<quote><systemitem class="ipaddress"
451
>2001:db8:f983:bd0b:30de:ae4a:71f2:f672</systemitem></quote>,
452
port 4711, using interface eth2:
456
<!-- do not wrap this line -->
457
<userinput>&COMMANDNAME; --debug --pubkey keydir/pubkey.txt --seckey keydir/seckey.txt --connect 2001:db8:f983:bd0b:30de:ae4a:71f2:f672:4711 --interface eth2</userinput>
380
463
<refsect1 id="security">
381
464
<title>SECURITY</title>
466
This program is set-uid to root, but will switch back to the
467
original (and presumably non-privileged) user and group after
468
bringing up the network interface.
471
To use this program for its intended purpose (see <xref
472
linkend="purpose"/>), the password for the root file system will
473
have to be given out to be stored in a server computer, after
474
having been encrypted using an OpenPGP key. This encrypted data
475
which will be stored in a server can only be decrypted by the
476
OpenPGP key, and the data will only be given out to those
477
clients who can prove they actually have that key. This key,
478
however, is stored unencrypted on the client side in its initial
479
<acronym>RAM</acronym> disk image file system. This is normally
480
readable by all, but this is normally fixed during installation
481
of this program; file permissions are set so that no-one is able
485
The only remaining weak point is that someone with physical
486
access to the client hard drive might turn off the client
487
computer, read the OpenPGP keys directly from the hard drive,
488
and communicate with the server. To safeguard against this, the
489
server is supposed to notice the client disappearing and stop
490
giving out the encrypted data. Therefore, it is important to
491
set the timeout and checker interval values tightly on the
492
server. See <citerefentry><refentrytitle
493
>mandos</refentrytitle><manvolnum>8</manvolnum></citerefentry>.
496
It will also help if the checker program on the server is
497
configured to request something from the client which can not be
498
spoofed by someone else on the network, unlike unencrypted
499
<acronym>ICMP</acronym> echo (<quote>ping</quote>) replies.
502
<emphasis>Note</emphasis>: This makes it completely insecure to
503
have <application >Mandos</application> clients which dual-boot
504
to another operating system which is <emphasis>not</emphasis>
505
trusted to keep the initial <acronym>RAM</acronym> disk image
386
510
<refsect1 id="see_also">
387
511
<title>SEE ALSO</title>
513
<citerefentry><refentrytitle>cryptsetup</refentrytitle>
514
<manvolnum>8</manvolnum></citerefentry>,
515
<citerefentry><refentrytitle>crypttab</refentrytitle>
516
<manvolnum>5</manvolnum></citerefentry>,
389
517
<citerefentry><refentrytitle>mandos</refentrytitle>
390
518
<manvolnum>8</manvolnum></citerefentry>,
391
519
<citerefentry><refentrytitle>password-prompt</refentrytitle>
393
521
<citerefentry><refentrytitle>plugin-runner</refentrytitle>
394
522
<manvolnum>8mandos</manvolnum></citerefentry>
398
<ulink url="http://www.zeroconf.org/">Zeroconf</ulink>
402
<ulink url="http://www.avahi.org/">Avahi</ulink>
407
url="http://www.gnu.org/software/gnutls/">GnuTLS</ulink>
412
url="http://www.gnupg.org/related_software/gpgme/"
417
<citation>RFC 4880: <citetitle>OpenPGP Message
418
Format</citetitle></citation>
422
<citation>RFC 5081: <citetitle>Using OpenPGP Keys for
423
Transport Layer Security</citetitle></citation>
427
<citation>RFC 4291: <citetitle>IP Version 6 Addressing
428
Architecture</citetitle>, section 2.5.6, Link-Local IPv6
429
Unicast Addresses</citation>
527
<ulink url="http://www.zeroconf.org/">Zeroconf</ulink>
531
Zeroconf is the network protocol standard used for finding
532
Mandos servers on the local network.
538
<ulink url="http://www.avahi.org/">Avahi</ulink>
542
Avahi is the library this program calls to find Zeroconf
549
<ulink url="http://www.gnu.org/software/gnutls/"
554
GnuTLS is the library this client uses to implement TLS for
555
communicating securely with the server, and at the same time
556
send the public OpenPGP key to the server.
562
<ulink url="http://www.gnupg.org/related_software/gpgme/"
567
GPGME is the library used to decrypt the OpenPGP data sent
574
RFC 4291: <citetitle>IP Version 6 Addressing
575
Architecture</citetitle>
580
<term>Section 2.2: <citetitle>Text Representation of
581
Addresses</citetitle></term>
582
<listitem><para/></listitem>
585
<term>Section 2.5.5.2: <citetitle>IPv4-Mapped IPv6
586
Address</citetitle></term>
587
<listitem><para/></listitem>
590
<term>Section 2.5.6, <citetitle>Link-Local IPv6 Unicast
591
Addresses</citetitle></term>
594
This client uses IPv6 link-local addresses, which are
595
immediately usable since a link-local addresses is
596
automatically assigned to a network interfaces when it
606
RFC 4346: <citetitle>The Transport Layer Security (TLS)
607
Protocol Version 1.1</citetitle>
611
TLS 1.1 is the protocol implemented by GnuTLS.
617
RFC 4880: <citetitle>OpenPGP Message Format</citetitle>
621
The data received from the server is binary encrypted
628
RFC 5081: <citetitle>Using OpenPGP Keys for Transport Layer
633
This is implemented by GnuTLS and used by this program so
634
that OpenPGP keys can be used.
435
642
<!-- Local Variables: -->
436
643
<!-- time-stamp-start: "<!ENTITY TIMESTAMP [\"']" -->
437
644
<!-- time-stamp-end: "[\"']>" -->