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 "2008-09-30">
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
47
<refname><command>&COMMANDNAME;</command></refname>
49
Client for <application>Mandos</application>
54
55
<command>&COMMANDNAME;</command>
56
57
<arg choice="plain"><option>--connect
57
<replaceable>IPADDR</replaceable><literal>:</literal
58
<replaceable>ADDRESS</replaceable><literal>:</literal
58
59
><replaceable>PORT</replaceable></option></arg>
59
60
<arg choice="plain"><option>-c
60
<replaceable>IPADDR</replaceable><literal>:</literal
61
<replaceable>ADDRESS</replaceable><literal>:</literal
61
62
><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
66
<arg choice="plain"><option>--interface
73
67
<replaceable>NAME</replaceable></option></arg>
74
68
<arg choice="plain"><option>-i
336
312
<filename>/etc/crypttab</filename>, but it would then be
337
313
impossible to enter a password for the encrypted root disk at
338
314
the console, since this program does not read from the console
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.
315
at all. This is why a separate plugin runner (<citerefentry>
316
<refentrytitle>plugin-runner</refentrytitle>
317
<manvolnum>8mandos</manvolnum></citerefentry>) is used to run
318
both this program and others in in parallel,
319
<emphasis>one</emphasis> of which will prompt for passwords on
418
399
</informalexample>
419
400
<informalexample>
421
Run in debug mode, and use a custom key directory:
402
Run in debug mode, and use a custom key:
424
<!-- do not wrap this line -->
425
<userinput>&COMMANDNAME; --debug --keydir keydir</userinput>
406
<!-- do not wrap this line -->
407
<userinput>&COMMANDNAME; --debug --pubkey keydir/pubkey.txt --seckey keydir/seckey.txt</userinput>
427
410
</informalexample>
428
411
<informalexample>
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
432
address <quote><systemitem class="ipaddress"
413
Run in debug mode, with a custom key, and do not use Zeroconf
414
to locate a server; connect directly to the IPv6 address
415
<quote><systemitem class="ipaddress"
433
416
>2001:db8:f983:bd0b:30de:ae4a:71f2:f672</systemitem></quote>,
434
417
port 4711, using interface eth2:
438
421
<!-- do not wrap this line -->
439
<userinput>&COMMANDNAME; --debug --keydir keydir --connect 2001:db8:f983:bd0b:30de:ae4a:71f2:f672:4711 --interface eth2</userinput>
422
<userinput>&COMMANDNAME; --debug --pubkey keydir/pubkey.txt --seckey keydir/seckey.txt --connect 2001:db8:f983:bd0b:30de:ae4a:71f2:f672:4711 --interface eth2</userinput>
442
425
</informalexample>
445
428
<refsect1 id="security">
446
429
<title>SECURITY</title>
431
This program is set-uid to root, but will switch back to the
432
original (and presumably non-privileged) user and group after
433
bringing up the network interface.
436
To use this program for its intended purpose (see <xref
437
linkend="purpose"/>), the password for the root file system will
438
have to be given out to be stored in a server computer, after
439
having been encrypted using an OpenPGP key. This encrypted data
440
which will be stored in a server can only be decrypted by the
441
OpenPGP key, and the data will only be given out to those
442
clients who can prove they actually have that key. This key,
443
however, is stored unencrypted on the client side in its initial
444
<acronym>RAM</acronym> disk image file system. This is normally
445
readable by all, but this is normally fixed during installation
446
of this program; file permissions are set so that no-one is able
450
The only remaining weak point is that someone with physical
451
access to the client hard drive might turn off the client
452
computer, read the OpenPGP keys directly from the hard drive,
453
and communicate with the server. To safeguard against this, the
454
server is supposed to notice the client disappearing and stop
455
giving out the encrypted data. Therefore, it is important to
456
set the timeout and checker interval values tightly on the
457
server. See <citerefentry><refentrytitle
458
>mandos</refentrytitle><manvolnum>8</manvolnum></citerefentry>.
461
It will also help if the checker program on the server is
462
configured to request something from the client which can not be
463
spoofed by someone else on the network, unlike unencrypted
464
<acronym>ICMP</acronym> echo (<quote>ping</quote>) replies.
467
<emphasis>Note</emphasis>: This makes it completely insecure to
468
have <application >Mandos</application> clients which dual-boot
469
to another operating system which is <emphasis>not</emphasis>
470
trusted to keep the initial <acronym>RAM</acronym> disk image
451
475
<refsect1 id="see_also">
452
476
<title>SEE ALSO</title>
478
<citerefentry><refentrytitle>cryptsetup</refentrytitle>
479
<manvolnum>8</manvolnum></citerefentry>,
480
<citerefentry><refentrytitle>crypttab</refentrytitle>
481
<manvolnum>5</manvolnum></citerefentry>,
454
482
<citerefentry><refentrytitle>mandos</refentrytitle>
455
483
<manvolnum>8</manvolnum></citerefentry>,
456
484
<citerefentry><refentrytitle>password-prompt</refentrytitle>
458
486
<citerefentry><refentrytitle>plugin-runner</refentrytitle>
459
487
<manvolnum>8mandos</manvolnum></citerefentry>
463
<ulink url="http://www.zeroconf.org/">Zeroconf</ulink>
467
<ulink url="http://www.avahi.org/">Avahi</ulink>
472
url="http://www.gnu.org/software/gnutls/">GnuTLS</ulink>
477
url="http://www.gnupg.org/related_software/gpgme/"
482
<citation>RFC 4880: <citetitle>OpenPGP Message
483
Format</citetitle></citation>
487
<citation>RFC 5081: <citetitle>Using OpenPGP Keys for
488
Transport Layer Security</citetitle></citation>
492
<citation>RFC 4291: <citetitle>IP Version 6 Addressing
493
Architecture</citetitle>, section 2.5.6, Link-Local IPv6
494
Unicast Addresses</citation>
492
<ulink url="http://www.zeroconf.org/">Zeroconf</ulink>
496
Zeroconf is the network protocol standard used for finding
497
Mandos servers on the local network.
503
<ulink url="http://www.avahi.org/">Avahi</ulink>
507
Avahi is the library this program calls to find Zeroconf
514
<ulink url="http://www.gnu.org/software/gnutls/"
519
GnuTLS is the library this client uses to implement TLS for
520
communicating securely with the server, and at the same time
521
send the public OpenPGP key to the server.
527
<ulink url="http://www.gnupg.org/related_software/gpgme/"
532
GPGME is the library used to decrypt the OpenPGP data sent
539
RFC 4291: <citetitle>IP Version 6 Addressing
540
Architecture</citetitle>
545
<term>Section 2.2: <citetitle>Text Representation of
546
Addresses</citetitle></term>
547
<listitem><para/></listitem>
550
<term>Section 2.5.5.2: <citetitle>IPv4-Mapped IPv6
551
Address</citetitle></term>
552
<listitem><para/></listitem>
555
<term>Section 2.5.6, <citetitle>Link-Local IPv6 Unicast
556
Addresses</citetitle></term>
559
This client uses IPv6 link-local addresses, which are
560
immediately usable since a link-local addresses is
561
automatically assigned to a network interfaces when it
571
RFC 4346: <citetitle>The Transport Layer Security (TLS)
572
Protocol Version 1.1</citetitle>
576
TLS 1.1 is the protocol implemented by GnuTLS.
582
RFC 4880: <citetitle>OpenPGP Message Format</citetitle>
586
The data received from the server is binary encrypted
593
RFC 5081: <citetitle>Using OpenPGP Keys for Transport Layer
598
This is implemented by GnuTLS and used by this program so
599
that OpenPGP keys can be used.
500
607
<!-- Local Variables: -->
501
608
<!-- time-stamp-start: "<!ENTITY TIMESTAMP [\"']" -->
502
609
<!-- time-stamp-end: "[\"']>" -->