46
46
<refname><command>&COMMANDNAME;</command></refname>
48
Client for <application>Mandos</application>
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
362
346
<refsect1 id="file">
363
347
<title>FILES</title>
350
<term><filename>/conf/conf.d/mandos/pubkey.txt</filename
352
<term><filename>/conf/conf.d/mandos/seckey.txt</filename
356
OpenPGP public and private key files, in <quote>ASCII
357
Armor</quote> format. These are the default file names,
358
they can be changed with the <option>--pubkey</option> and
359
<option>--seckey</option> options.
366
<!-- <refsect1 id="bugs"> -->
367
<!-- <title>BUGS</title> -->
374
372
<refsect1 id="example">
375
373
<title>EXAMPLE</title>
375
Note that normally, command line options will not be given
376
directly, but via options for the Mandos <citerefentry
377
><refentrytitle>plugin-runner</refentrytitle>
378
<manvolnum>8mandos</manvolnum></citerefentry>.
382
Normal invocation needs no options, if the network interface
383
is <quote>eth0</quote>:
386
<userinput>&COMMANDNAME;</userinput>
391
Search for Mandos servers (and connect to them) using another
395
<!-- do not wrap this line -->
396
<userinput>&COMMANDNAME; --interface eth1</userinput>
401
Run in debug mode, and use a custom key:
405
<!-- do not wrap this line -->
406
<userinput>&COMMANDNAME; --debug --pubkey keydir/pubkey.txt --seckey keydir/seckey.txt</userinput>
412
Run in debug mode, with a custom key, and do not use Zeroconf
413
to locate a server; connect directly to the IPv6 address
414
<quote><systemitem class="ipaddress"
415
>2001:db8:f983:bd0b:30de:ae4a:71f2:f672</systemitem></quote>,
416
port 4711, using interface eth2:
420
<!-- do not wrap this line -->
421
<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
427
<refsect1 id="security">
381
428
<title>SECURITY</title>
430
This program is set-uid to root, but will switch back to the
431
original (and presumably non-privileged) user and group after
432
bringing up the network interface.
435
To use this program for its intended purpose (see <xref
436
linkend="purpose"/>), the password for the root file system will
437
have to be given out to be stored in a server computer, after
438
having been encrypted using an OpenPGP key. This encrypted data
439
which will be stored in a server can only be decrypted by the
440
OpenPGP key, and the data will only be given out to those
441
clients who can prove they actually have that key. This key,
442
however, is stored unencrypted on the client side in its initial
443
<acronym>RAM</acronym> disk image file system. This is normally
444
readable by all, but this is normally fixed during installation
445
of this program; file permissions are set so that no-one is able
449
The only remaining weak point is that someone with physical
450
access to the client hard drive might turn off the client
451
computer, read the OpenPGP keys directly from the hard drive,
452
and communicate with the server. The defense against this is
453
that the server is supposed to notice the client disappearing
454
and will stop giving out the encrypted data. Therefore, it is
455
important to set the timeout and checker interval values tightly
456
on the server. See <citerefentry><refentrytitle
457
>mandos</refentrytitle><manvolnum>8</manvolnum></citerefentry>.
460
It will also help if the checker program on the server is
461
configured to request something from the client which can not be
462
spoofed by someone else on the network, unlike unencrypted
463
<acronym>ICMP</acronym> echo (<quote>ping</quote>) replies.
466
<emphasis>Note</emphasis>: This makes it completely insecure to
467
have <application >Mandos</application> clients which dual-boot
468
to another operating system which is <emphasis>not</emphasis>
469
trusted to keep the initial <acronym>RAM</acronym> disk image
386
474
<refsect1 id="see_also">
387
475
<title>SEE ALSO</title>
477
<citerefentry><refentrytitle>cryptsetup</refentrytitle>
478
<manvolnum>8</manvolnum></citerefentry>,
479
<citerefentry><refentrytitle>crypttab</refentrytitle>
480
<manvolnum>5</manvolnum></citerefentry>,
389
481
<citerefentry><refentrytitle>mandos</refentrytitle>
390
482
<manvolnum>8</manvolnum></citerefentry>,
391
483
<citerefentry><refentrytitle>password-prompt</refentrytitle>
393
485
<citerefentry><refentrytitle>plugin-runner</refentrytitle>
394
486
<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>
491
<ulink url="http://www.zeroconf.org/">Zeroconf</ulink>
495
Zeroconf is the network protocol standard used for finding
496
Mandos servers on the local network.
502
<ulink url="http://www.avahi.org/">Avahi</ulink>
506
Avahi is the library this program calls to find Zeroconf
513
<ulink url="http://www.gnu.org/software/gnutls/"
518
GnuTLS is the library this client uses to implement TLS for
519
communicating securely with the server, and at the same time
520
send the public OpenPGP key to the server.
526
<ulink url="http://www.gnupg.org/related_software/gpgme/"
531
GPGME is the library used to decrypt the OpenPGP data sent
538
RFC 4291: <citetitle>IP Version 6 Addressing
539
Architecture</citetitle>
544
<term>Section 2.2: <citetitle>Text Representation of
545
Addresses</citetitle></term>
546
<listitem><para/></listitem>
549
<term>Section 2.5.5.2: <citetitle>IPv4-Mapped IPv6
550
Address</citetitle></term>
551
<listitem><para/></listitem>
554
<term>Section 2.5.6, <citetitle>Link-Local IPv6 Unicast
555
Addresses</citetitle></term>
558
This client uses IPv6 link-local addresses, which are
559
immediately usable since a link-local addresses is
560
automatically assigned to a network interfaces when it
570
RFC 4346: <citetitle>The Transport Layer Security (TLS)
571
Protocol Version 1.1</citetitle>
575
TLS 1.1 is the protocol implemented by GnuTLS.
581
RFC 4880: <citetitle>OpenPGP Message Format</citetitle>
585
The data received from the server is binary encrypted
592
RFC 5081: <citetitle>Using OpenPGP Keys for Transport Layer
597
This is implemented by GnuTLS and used by this program so
598
that OpenPGP keys can be used.
435
606
<!-- Local Variables: -->
436
607
<!-- time-stamp-start: "<!ENTITY TIMESTAMP [\"']" -->
437
608
<!-- time-stamp-end: "[\"']>" -->