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 COMMANDNAME "mandos-client">
5
<!ENTITY TIMESTAMP "2009-02-09">
6
<!ENTITY % common SYSTEM "../common.ent">
4
<!ENTITY VERSION "1.0">
5
<!ENTITY COMMANDNAME "password-request">
6
<!ENTITY TIMESTAMP "2008-09-03">
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>
48
46
<refname><command>&COMMANDNAME;</command></refname>
50
Client for <application>Mandos</application>
56
54
<command>&COMMANDNAME;</command>
58
56
<arg choice="plain"><option>--connect
59
<replaceable>ADDRESS</replaceable><literal>:</literal
57
<replaceable>IPADDR</replaceable><literal>:</literal
60
58
><replaceable>PORT</replaceable></option></arg>
61
59
<arg choice="plain"><option>-c
62
<replaceable>ADDRESS</replaceable><literal>:</literal
60
<replaceable>IPADDR</replaceable><literal>:</literal
63
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>
67
72
<arg choice="plain"><option>--interface
68
73
<replaceable>NAME</replaceable></option></arg>
69
74
<arg choice="plain"><option>-i
121
122
</refsynopsisdiv>
123
124
<refsect1 id="description">
124
125
<title>DESCRIPTION</title>
126
127
<command>&COMMANDNAME;</command> is a client program that
127
128
communicates with <citerefentry><refentrytitle
128
129
>mandos</refentrytitle><manvolnum>8</manvolnum></citerefentry>
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
130
to get a password. It uses IPv6 link-local addresses to get
131
network connectivity, Zeroconf to find servers, and TLS with an
132
OpenPGP key to ensure authenticity and confidentiality. It
133
keeps running, trying all servers on the network, until it
134
receives a satisfactory reply or a TERM signal is recieved.
141
137
This program is not meant to be run directly; it is really meant
198
<term><option>--interface=<replaceable
199
>NAME</replaceable></option></term>
194
<term><option>--keydir=<replaceable
195
>DIRECTORY</replaceable></option></term>
197
<replaceable>DIRECTORY</replaceable></option></term>
200
Directory to read the OpenPGP key files
201
<filename>pubkey.txt</filename> and
202
<filename>seckey.txt</filename> from. The default is
203
<filename>/conf/conf.d/mandos</filename> (in the initial
204
<acronym>RAM</acronym> disk environment).
210
<term><option>--interface=
211
<replaceable>NAME</replaceable></option></term>
201
213
<replaceable>NAME</replaceable></option></term>
204
216
Network interface that will be brought up and scanned for
205
Mandos servers to connect to. The default is
217
Mandos servers to connect to. The default it
206
218
<quote><literal>eth0</literal></quote>.
210
222
specifies the interface to use to connect to the address
214
Note that since this program will normally run in the
215
initial RAM disk environment, the interface must be an
216
interface which exists at that stage. Thus, the interface
217
can not be a pseudo-interface such as <quote>br0</quote>
218
or <quote>tun0</quote>; such interfaces will not exist
219
until much later in the boot process, and can not be used
223
<replaceable>NAME</replaceable> can be the empty string;
224
this will not use any specific interface, and will not
225
bring up an interface on startup. This is not
226
recommended, and only meant for advanced users.
235
232
<replaceable>FILE</replaceable></option></term>
238
OpenPGP public key file name. The default name is
239
<quote><filename>/conf/conf.d/mandos/pubkey.txt</filename
235
OpenPGP public key file base name. This will be combined
236
with the directory from the <option>--keydir</option>
237
option to form an absolute file name. The default name is
238
<quote><literal>pubkey.txt</literal></quote>.
246
244
<term><option>--seckey=<replaceable
247
245
>FILE</replaceable></option></term>
249
247
<replaceable>FILE</replaceable></option></term>
252
OpenPGP secret key file name. The default name is
253
<quote><filename>/conf/conf.d/mandos/seckey.txt</filename
250
OpenPGP secret key file base name. This will be combined
251
with the directory from the <option>--keydir</option>
252
option to form an absolute file name. The default name is
253
<quote><literal>seckey.txt</literal></quote>.
280
<term><option>--delay=<replaceable
281
>SECONDS</replaceable></option></term>
284
After bringing the network interface up, the program waits
285
for the interface to arrive in a <quote>running</quote>
286
state before proceeding. During this time, the kernel log
287
level will be lowered to reduce clutter on the system
288
console, alleviating any other plugins which might be
289
using the system console. This option sets the upper
290
limit of seconds to wait. The default is 2.5 seconds.
296
279
<term><option>--debug</option></term>
353
336
<filename>/etc/crypttab</filename>, but it would then be
354
337
impossible to enter a password for the encrypted root disk at
355
338
the console, since this program does not read from the console
356
at all. This is why a separate plugin runner (<citerefentry>
357
<refentrytitle>plugin-runner</refentrytitle>
358
<manvolnum>8mandos</manvolnum></citerefentry>) is used to run
359
both this program and others in in parallel,
360
<emphasis>one</emphasis> of which will prompt for passwords on
339
at all. This is why a separate plugin does that, which will be
340
run in parallell to this one by the plugin runner.
440
418
</informalexample>
441
419
<informalexample>
443
Run in debug mode, and use a custom key:
421
Run in debug mode, and use a custom key directory:
447
<!-- do not wrap this line -->
448
<userinput>&COMMANDNAME; --debug --pubkey keydir/pubkey.txt --seckey keydir/seckey.txt</userinput>
424
<!-- do not wrap this line -->
425
<userinput>&COMMANDNAME; --debug --keydir keydir</userinput>
451
427
</informalexample>
452
428
<informalexample>
454
Run in debug mode, with a custom key, and do not use Zeroconf
455
to locate a server; connect directly to the IPv6 link-local
430
Run in debug mode, with a custom key directory, and do not use
431
Zeroconf to locate a server; connect directly to the IPv6
456
432
address <quote><systemitem class="ipaddress"
457
>fe80::aede:48ff:fe71:f6f2</systemitem></quote>, port 4711,
458
using interface eth2:
433
>2001:db8:f983:bd0b:30de:ae4a:71f2:f672</systemitem></quote>,
434
port 4711, using interface eth2:
462
438
<!-- do not wrap this line -->
463
<userinput>&COMMANDNAME; --debug --pubkey keydir/pubkey.txt --seckey keydir/seckey.txt --connect fe80::aede:48ff:fe71:f6f2:4711 --interface eth2</userinput>
439
<userinput>&COMMANDNAME; --debug --keydir keydir --connect 2001:db8:f983:bd0b:30de:ae4a:71f2:f672:4711 --interface eth2</userinput>
466
442
</informalexample>
469
445
<refsect1 id="security">
470
446
<title>SECURITY</title>
472
448
This program is set-uid to root, but will switch back to the
473
original (and presumably non-privileged) user and group after
474
bringing up the network interface.
449
original user and group after bringing up the network interface.
477
452
To use this program for its intended purpose (see <xref
491
466
The only remaining weak point is that someone with physical
492
467
access to the client hard drive might turn off the client
493
468
computer, read the OpenPGP keys directly from the hard drive,
494
and communicate with the server. To safeguard against this, the
495
server is supposed to notice the client disappearing and stop
496
giving out the encrypted data. Therefore, it is important to
497
set the timeout and checker interval values tightly on the
498
server. See <citerefentry><refentrytitle
469
and communicate with the server. The defense against this is
470
that the server is supposed to notice the client disappearing
471
and will stop giving out the encrypted data. Therefore, it is
472
important to set the timeout and checker interval values tightly
473
on the server. See <citerefentry><refentrytitle
499
474
>mandos</refentrytitle><manvolnum>8</manvolnum></citerefentry>.
502
It will also help if the checker program on the server is
503
configured to request something from the client which can not be
504
spoofed by someone else on the network, unlike unencrypted
505
<acronym>ICMP</acronym> echo (<quote>ping</quote>) replies.
508
<emphasis>Note</emphasis>: This makes it completely insecure to
509
have <application >Mandos</application> clients which dual-boot
510
to another operating system which is <emphasis>not</emphasis>
511
trusted to keep the initial <acronym>RAM</acronym> disk image
477
<emphasis>Note</emphasis>: This makes it impossible to have
478
<application >Mandos</application> clients which dual-boot to
479
another operating system which does <emphasis>not</emphasis> run
480
a <application>Mandos</application> client.
516
484
<refsect1 id="see_also">
517
485
<title>SEE ALSO</title>
519
<citerefentry><refentrytitle>cryptsetup</refentrytitle>
520
<manvolnum>8</manvolnum></citerefentry>,
521
<citerefentry><refentrytitle>crypttab</refentrytitle>
522
<manvolnum>5</manvolnum></citerefentry>,
523
487
<citerefentry><refentrytitle>mandos</refentrytitle>
524
488
<manvolnum>8</manvolnum></citerefentry>,
525
489
<citerefentry><refentrytitle>password-prompt</refentrytitle>
527
491
<citerefentry><refentrytitle>plugin-runner</refentrytitle>
528
492
<manvolnum>8mandos</manvolnum></citerefentry>
533
<ulink url="http://www.zeroconf.org/">Zeroconf</ulink>
537
Zeroconf is the network protocol standard used for finding
538
Mandos servers on the local network.
544
<ulink url="http://www.avahi.org/">Avahi</ulink>
548
Avahi is the library this program calls to find Zeroconf
555
<ulink url="http://www.gnu.org/software/gnutls/"
560
GnuTLS is the library this client uses to implement TLS for
561
communicating securely with the server, and at the same time
562
send the public OpenPGP key to the server.
568
<ulink url="http://www.gnupg.org/related_software/gpgme/"
573
GPGME is the library used to decrypt the OpenPGP data sent
580
RFC 4291: <citetitle>IP Version 6 Addressing
581
Architecture</citetitle>
586
<term>Section 2.2: <citetitle>Text Representation of
587
Addresses</citetitle></term>
588
<listitem><para/></listitem>
591
<term>Section 2.5.5.2: <citetitle>IPv4-Mapped IPv6
592
Address</citetitle></term>
593
<listitem><para/></listitem>
596
<term>Section 2.5.6, <citetitle>Link-Local IPv6 Unicast
597
Addresses</citetitle></term>
600
This client uses IPv6 link-local addresses, which are
601
immediately usable since a link-local addresses is
602
automatically assigned to a network interfaces when it
612
RFC 4346: <citetitle>The Transport Layer Security (TLS)
613
Protocol Version 1.1</citetitle>
617
TLS 1.1 is the protocol implemented by GnuTLS.
623
RFC 4880: <citetitle>OpenPGP Message Format</citetitle>
627
The data received from the server is binary encrypted
634
RFC 5081: <citetitle>Using OpenPGP Keys for Transport Layer
639
This is implemented by GnuTLS and used by this program so
640
that OpenPGP keys can be used.
496
<ulink url="http://www.zeroconf.org/">Zeroconf</ulink>
500
<ulink url="http://www.avahi.org/">Avahi</ulink>
505
url="http://www.gnu.org/software/gnutls/">GnuTLS</ulink>
510
url="http://www.gnupg.org/related_software/gpgme/"
515
<citation>RFC 4880: <citetitle>OpenPGP Message
516
Format</citetitle></citation>
520
<citation>RFC 5081: <citetitle>Using OpenPGP Keys for
521
Transport Layer Security</citetitle></citation>
525
<citation>RFC 4291: <citetitle>IP Version 6 Addressing
526
Architecture</citetitle>, section 2.5.6, Link-Local IPv6
527
Unicast Addresses</citation>
648
533
<!-- Local Variables: -->
649
534
<!-- time-stamp-start: "<!ENTITY TIMESTAMP [\"']" -->
650
535
<!-- time-stamp-end: "[\"']>" -->