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-04">
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
336
313
<filename>/etc/crypttab</filename>, but it would then be
337
314
impossible to enter a password for the encrypted root disk at
338
315
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.
316
at all. This is why a separate plugin runner (<citerefentry>
317
<refentrytitle>plugin-runner</refentrytitle>
318
<manvolnum>8mandos</manvolnum></citerefentry>) is used to run
319
both this program and others in in parallel,
320
<emphasis>one</emphasis> of which will prompt for passwords on
418
400
</informalexample>
419
401
<informalexample>
421
Run in debug mode, and use a custom key directory:
403
Run in debug mode, and use a custom key:
424
<!-- do not wrap this line -->
425
<userinput>&COMMANDNAME; --debug --keydir keydir</userinput>
407
<!-- do not wrap this line -->
408
<userinput>&COMMANDNAME; --debug --pubkey keydir/pubkey.txt --seckey keydir/seckey.txt</userinput>
427
411
</informalexample>
428
412
<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"
414
Run in debug mode, with a custom key, and do not use Zeroconf
415
to locate a server; connect directly to the IPv6 address
416
<quote><systemitem class="ipaddress"
433
417
>2001:db8:f983:bd0b:30de:ae4a:71f2:f672</systemitem></quote>,
434
418
port 4711, using interface eth2:
438
422
<!-- do not wrap this line -->
439
<userinput>&COMMANDNAME; --debug --keydir keydir --connect 2001:db8:f983:bd0b:30de:ae4a:71f2:f672:4711 --interface eth2</userinput>
423
<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
426
</informalexample>
445
429
<refsect1 id="security">
446
430
<title>SECURITY</title>
432
This program is set-uid to root, but will switch back to the
433
original (and presumably non-privileged) user and group after
434
bringing up the network interface.
437
To use this program for its intended purpose (see <xref
438
linkend="purpose"/>), the password for the root file system will
439
have to be given out to be stored in a server computer, after
440
having been encrypted using an OpenPGP key. This encrypted data
441
which will be stored in a server can only be decrypted by the
442
OpenPGP key, and the data will only be given out to those
443
clients who can prove they actually have that key. This key,
444
however, is stored unencrypted on the client side in its initial
445
<acronym>RAM</acronym> disk image file system. This is normally
446
readable by all, but this is normally fixed during installation
447
of this program; file permissions are set so that no-one is able
451
The only remaining weak point is that someone with physical
452
access to the client hard drive might turn off the client
453
computer, read the OpenPGP keys directly from the hard drive,
454
and communicate with the server. To safeguard against this, the
455
server is supposed to notice the client disappearing and stop
456
giving out the encrypted data. Therefore, it is important to
457
set the timeout and checker interval values tightly on the
458
server. See <citerefentry><refentrytitle
459
>mandos</refentrytitle><manvolnum>8</manvolnum></citerefentry>.
462
It will also help if the checker program on the server is
463
configured to request something from the client which can not be
464
spoofed by someone else on the network, unlike unencrypted
465
<acronym>ICMP</acronym> echo (<quote>ping</quote>) replies.
468
<emphasis>Note</emphasis>: This makes it completely insecure to
469
have <application >Mandos</application> clients which dual-boot
470
to another operating system which is <emphasis>not</emphasis>
471
trusted to keep the initial <acronym>RAM</acronym> disk image
451
476
<refsect1 id="see_also">
452
477
<title>SEE ALSO</title>
479
<citerefentry><refentrytitle>cryptsetup</refentrytitle>
480
<manvolnum>8</manvolnum></citerefentry>,
481
<citerefentry><refentrytitle>crypttab</refentrytitle>
482
<manvolnum>5</manvolnum></citerefentry>,
454
483
<citerefentry><refentrytitle>mandos</refentrytitle>
455
484
<manvolnum>8</manvolnum></citerefentry>,
456
485
<citerefentry><refentrytitle>password-prompt</refentrytitle>
458
487
<citerefentry><refentrytitle>plugin-runner</refentrytitle>
459
488
<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>
493
<ulink url="http://www.zeroconf.org/">Zeroconf</ulink>
497
Zeroconf is the network protocol standard used for finding
498
Mandos servers on the local network.
504
<ulink url="http://www.avahi.org/">Avahi</ulink>
508
Avahi is the library this program calls to find Zeroconf
515
<ulink url="http://www.gnu.org/software/gnutls/"
520
GnuTLS is the library this client uses to implement TLS for
521
communicating securely with the server, and at the same time
522
send the public OpenPGP key to the server.
528
<ulink url="http://www.gnupg.org/related_software/gpgme/"
533
GPGME is the library used to decrypt the OpenPGP data sent
540
RFC 4291: <citetitle>IP Version 6 Addressing
541
Architecture</citetitle>
546
<term>Section 2.2: <citetitle>Text Representation of
547
Addresses</citetitle></term>
548
<listitem><para/></listitem>
551
<term>Section 2.5.5.2: <citetitle>IPv4-Mapped IPv6
552
Address</citetitle></term>
553
<listitem><para/></listitem>
556
<term>Section 2.5.6, <citetitle>Link-Local IPv6 Unicast
557
Addresses</citetitle></term>
560
This client uses IPv6 link-local addresses, which are
561
immediately usable since a link-local addresses is
562
automatically assigned to a network interfaces when it
572
RFC 4346: <citetitle>The Transport Layer Security (TLS)
573
Protocol Version 1.1</citetitle>
577
TLS 1.1 is the protocol implemented by GnuTLS.
583
RFC 4880: <citetitle>OpenPGP Message Format</citetitle>
587
The data received from the server is binary encrypted
594
RFC 5081: <citetitle>Using OpenPGP Keys for Transport Layer
599
This is implemented by GnuTLS and used by this program so
600
that OpenPGP keys can be used.
500
608
<!-- Local Variables: -->
501
609
<!-- time-stamp-start: "<!ENTITY TIMESTAMP [\"']" -->
502
610
<!-- time-stamp-end: "[\"']>" -->