50
69
<refname><command>&COMMANDNAME;</command></refname>
52
Client for <application>Mandos</application>
58
77
<command>&COMMANDNAME;</command>
60
<arg choice="plain"><option>--connect
61
<replaceable>ADDRESS</replaceable><literal>:</literal
62
><replaceable>PORT</replaceable></option></arg>
63
<arg choice="plain"><option>-c
64
<replaceable>ADDRESS</replaceable><literal>:</literal
65
><replaceable>PORT</replaceable></option></arg>
69
<arg choice="plain"><option>--interface
70
<replaceable>NAME</replaceable><arg rep='repeat'
71
>,<replaceable>NAME</replaceable></arg></option></arg>
72
<arg choice="plain"><option>-i <replaceable>NAME</replaceable
73
><arg rep='repeat'>,<replaceable>NAME</replaceable></arg
78
<arg choice="plain"><option>--pubkey
79
<replaceable>FILE</replaceable></option></arg>
80
<arg choice="plain"><option>-p
81
<replaceable>FILE</replaceable></option></arg>
85
<arg choice="plain"><option>--seckey
86
<replaceable>FILE</replaceable></option></arg>
87
<arg choice="plain"><option>-s
88
<replaceable>FILE</replaceable></option></arg>
92
<option>--priority <replaceable>STRING</replaceable></option>
96
<option>--dh-bits <replaceable>BITS</replaceable></option>
100
<option>--delay <replaceable>SECONDS</replaceable></option>
104
<option>--retry <replaceable>SECONDS</replaceable></option>
108
<option>--network-hook-dir
109
<replaceable>DIR</replaceable></option>
113
<option>--debug</option>
117
<command>&COMMANDNAME;</command>
119
<arg choice="plain"><option>--help</option></arg>
120
<arg choice="plain"><option>-?</option></arg>
124
<command>&COMMANDNAME;</command>
125
<arg choice="plain"><option>--usage</option></arg>
128
<command>&COMMANDNAME;</command>
130
<arg choice="plain"><option>--version</option></arg>
131
<arg choice="plain"><option>-V</option></arg>
78
<arg choice='opt'>--connect<arg choice='plain'>IP</arg></arg>
79
<arg choice='opt'>--keydir<arg choice='plain'>KEYDIR</arg></arg>
80
<arg choice='opt'>--interface<arg choice='plain'>INTERFACE</arg></arg>
81
<arg choice='opt'>--pubkey<arg choice='plain'>PUBKEY</arg></arg>
82
<arg choice='opt'>--seckey<arg choice='plain'>SECKEY</arg></arg>
83
<arg choice='opt'>--priority<arg choice='plain'>PRIORITY</arg></arg>
84
<arg choice='opt'>--dh-bits<arg choice='plain'>BITS</arg></arg>
85
<arg choice='opt'>--debug</arg>
88
<command>&COMMANDNAME;</command>
89
<arg choice='plain'>--help</arg>
92
<command>&COMMANDNAME;</command>
93
<arg choice='plain'>--usage</arg>
96
<command>&COMMANDNAME;</command>
97
<arg choice='plain'>--version</arg>
136
101
<refsect1 id="description">
137
102
<title>DESCRIPTION</title>
139
<command>&COMMANDNAME;</command> is a client program that
140
communicates with <citerefentry><refentrytitle
141
>mandos</refentrytitle><manvolnum>8</manvolnum></citerefentry>
142
to get a password. In slightly more detail, this client program
143
brings up network interfaces, uses the interfaces’ IPv6
144
link-local addresses to get network connectivity, uses Zeroconf
145
to find servers on the local network, and communicates with
146
servers using TLS with an OpenPGP key to ensure authenticity and
147
confidentiality. This client program keeps running, trying all
148
servers on the network, until it receives a satisfactory reply
149
or a TERM signal. After all servers have been tried, all
150
servers are periodically retried. If no servers are found it
151
will wait indefinitely for new servers to appear.
154
The network interfaces are selected like this: If any interfaces
155
are specified using the <option>--interface</option> option,
156
those interface are used. Otherwise,
157
<command>&COMMANDNAME;</command> will use all interfaces that
158
are not loopback interfaces, are not point-to-point interfaces,
159
are capable of broadcasting and do not have the NOARP flag (see
160
<citerefentry><refentrytitle>netdevice</refentrytitle>
161
<manvolnum>7</manvolnum></citerefentry>). (If the
162
<option>--connect</option> option is used, point-to-point
163
interfaces and non-broadcast interfaces are accepted.) If any
164
used interfaces are not up and running, they are first taken up
165
(and later taken down again on program exit).
168
Before network interfaces are selected, all <quote>network
169
hooks</quote> are run; see <xref linkend="network-hooks"/>.
172
This program is not meant to be run directly; it is really meant
173
to run as a plugin of the <application>Mandos</application>
174
<citerefentry><refentrytitle>plugin-runner</refentrytitle>
175
<manvolnum>8mandos</manvolnum></citerefentry>, which runs in the
176
initial <acronym>RAM</acronym> disk environment because it is
177
specified as a <quote>keyscript</quote> in the <citerefentry>
178
<refentrytitle>crypttab</refentrytitle><manvolnum>5</manvolnum>
179
</citerefentry> file.
183
<refsect1 id="purpose">
184
<title>PURPOSE</title>
186
The purpose of this is to enable <emphasis>remote and unattended
187
rebooting</emphasis> of client host computer with an
188
<emphasis>encrypted root file system</emphasis>. See <xref
189
linkend="overview"/> for details.
104
<command>&COMMANDNAME;</command> is a mandos plugin that works
105
like a client program that through avahi detects mandos servers,
106
sets up a gnutls connect and request a encrypted password. Any
107
passwords given is automaticly decrypted and passed to
193
112
<refsect1 id="options">
194
113
<title>OPTIONS</title>
196
This program is commonly not invoked from the command line; it
197
is normally started by the <application>Mandos</application>
198
plugin runner, see <citerefentry><refentrytitle
199
>plugin-runner</refentrytitle><manvolnum>8mandos</manvolnum>
200
</citerefentry>. Any command line options this program accepts
201
are therefore normally provided by the plugin runner, and not
115
Commonly not invoked as command lines but from configuration
116
file of plugin runner.
207
<term><option>--connect=<replaceable
208
>ADDRESS</replaceable><literal>:</literal><replaceable
209
>PORT</replaceable></option></term>
211
<replaceable>ADDRESS</replaceable><literal>:</literal
212
><replaceable>PORT</replaceable></option></term>
215
Do not use Zeroconf to locate servers. Connect directly
216
to only one specified <application>Mandos</application>
217
server. Note that an IPv6 address has colon characters in
218
it, so the <emphasis>last</emphasis> colon character is
219
assumed to separate the address from the port number.
222
This option is normally only useful for testing and
229
<term><option>--interface=<replaceable
230
>NAME</replaceable><arg rep='repeat'>,<replaceable
231
>NAME</replaceable></arg></option></term>
233
<replaceable>NAME</replaceable><arg rep='repeat'>,<replaceable
234
>NAME</replaceable></arg></option></term>
237
Comma separated list of network interfaces that will be
238
brought up and scanned for Mandos servers to connect to.
239
The default is the empty string, which will automatically
240
use all appropriate interfaces.
243
If the <option>--connect</option> option is used, and
244
exactly one interface name is specified (except
245
<quote><literal>none</literal></quote>), this specifies
246
the interface to use to connect to the address given.
249
Note that since this program will normally run in the
250
initial RAM disk environment, the interface must be an
251
interface which exists at that stage. Thus, the interface
252
can normally not be a pseudo-interface such as
253
<quote>br0</quote> or <quote>tun0</quote>; such interfaces
254
will not exist until much later in the boot process, and
255
can not be used by this program, unless created by a
256
<quote>network hook</quote> — see <xref
257
linkend="network-hooks"/>.
260
<replaceable>NAME</replaceable> can be the string
261
<quote><literal>none</literal></quote>; this will make
262
<command>&COMMANDNAME;</command> not bring up
263
<emphasis>any</emphasis> interfaces specified
264
<emphasis>after</emphasis> this string. This is not
265
recommended, and only meant for advanced users.
271
<term><option>--pubkey=<replaceable
272
>FILE</replaceable></option></term>
274
<replaceable>FILE</replaceable></option></term>
277
OpenPGP public key file name. The default name is
278
<quote><filename>/conf/conf.d/mandos/pubkey.txt</filename
285
<term><option>--seckey=<replaceable
286
>FILE</replaceable></option></term>
288
<replaceable>FILE</replaceable></option></term>
291
OpenPGP secret key file name. The default name is
292
<quote><filename>/conf/conf.d/mandos/seckey.txt</filename
299
<term><option>--priority=<replaceable
300
>STRING</replaceable></option></term>
302
<xi:include href="../mandos-options.xml"
303
xpointer="priority"/>
308
<term><option>--dh-bits=<replaceable
309
>BITS</replaceable></option></term>
312
Sets the number of bits to use for the prime number in the
313
TLS Diffie-Hellman key exchange. Default is 1024.
319
<term><option>--delay=<replaceable
320
>SECONDS</replaceable></option></term>
323
After bringing a network interface up, the program waits
324
for the interface to arrive in a <quote>running</quote>
325
state before proceeding. During this time, the kernel log
326
level will be lowered to reduce clutter on the system
327
console, alleviating any other plugins which might be
328
using the system console. This option sets the upper
329
limit of seconds to wait. The default is 2.5 seconds.
335
<term><option>--retry=<replaceable
336
>SECONDS</replaceable></option></term>
339
All Mandos servers are tried repeatedly until a password
340
is received. This value specifies, in seconds, how long
341
between each successive try <emphasis>for the same
342
server</emphasis>. The default is 10 seconds.
348
<term><option>--network-hook-dir=<replaceable
349
>DIR</replaceable></option></term>
352
Network hook directory. The default directory is
353
<quote><filename class="directory"
354
>/lib/mandos/network-hooks.d</filename></quote>.
360
<term><option>--debug</option></term>
363
Enable debug mode. This will enable a lot of output to
364
standard error about what the program is doing. The
365
program will still perform all other functions normally.
368
It will also enable debug mode in the Avahi and GnuTLS
369
libraries, making them print large amounts of debugging
376
<term><option>--help</option></term>
377
<term><option>-?</option></term>
380
Gives a help message about options and their meanings.
386
<term><option>--usage</option></term>
389
Gives a short usage message.
395
<term><option>--version</option></term>
396
<term><option>-V</option></term>
399
Prints the program version.
121
<term><literal>-c</literal>, <literal>--connect=<replaceable>
122
IP</replaceable></literal></term>
125
Connect directly to a specified mandos server
131
<term><literal>-d</literal>, <literal>--keydir=<replaceable>
132
KEYDIR</replaceable></literal></term>
135
Directory where the openpgp keyring is
141
<term><literal>-i</literal>, <literal>--interface=
142
<replaceable>INTERFACE</replaceable></literal></term>
145
Interface that Avahi will conntect through
151
<term><literal>-p</literal>, <literal>--pubkey=<replaceable>
152
PUBKEY</replaceable></literal></term>
155
Public openpgp key for gnutls authentication
161
<term><literal>-s</literal>, <literal>--seckey=<replaceable>
162
SECKEY</replaceable></literal></term>
165
Secret openpgp key for gnutls authentication
171
<term><literal>--priority=<replaceable>PRIORITY</replaceable>
181
<term><literal>--dh-bits=<replaceable>BITS</replaceable>
185
dh-bits to use in gnutls communication
191
<term><literal>--debug</literal></term>
200
<term><literal>-?</literal>, <literal>--help</literal></term>
209
<term><literal>--usage</literal></term>
212
Gives a short usage message
218
<term><literal>-V</literal>, <literal>--version</literal></term>
221
Prints the program version
406
<refsect1 id="overview">
407
<title>OVERVIEW</title>
408
<xi:include href="../overview.xml"/>
410
This program is the client part. It is a plugin started by
411
<citerefentry><refentrytitle>plugin-runner</refentrytitle>
412
<manvolnum>8mandos</manvolnum></citerefentry> which will run in
413
an initial <acronym>RAM</acronym> disk environment.
416
This program could, theoretically, be used as a keyscript in
417
<filename>/etc/crypttab</filename>, but it would then be
418
impossible to enter a password for the encrypted root disk at
419
the console, since this program does not read from the console
420
at all. This is why a separate plugin runner (<citerefentry>
421
<refentrytitle>plugin-runner</refentrytitle>
422
<manvolnum>8mandos</manvolnum></citerefentry>) is used to run
423
both this program and others in in parallel,
424
<emphasis>one</emphasis> of which (<citerefentry>
425
<refentrytitle>password-prompt</refentrytitle>
426
<manvolnum>8mandos</manvolnum></citerefentry>) will prompt for
427
passwords on the system console.
431
228
<refsect1 id="exit_status">
432
229
<title>EXIT STATUS</title>
434
This program will exit with a successful (zero) exit status if a
435
server could be found and the password received from it could be
436
successfully decrypted and output on standard output. The
437
program will exit with a non-zero exit status only if a critical
438
error occurs. Otherwise, it will forever connect to any
439
discovered <application>Mandos</application> servers, trying to
440
get a decryptable password and print it.
444
234
<refsect1 id="environment">
445
235
<title>ENVIRONMENT</title>
447
This program does not use any environment variables, not even
448
the ones provided by <citerefentry><refentrytitle
449
>cryptsetup</refentrytitle><manvolnum>8</manvolnum>
454
<refsect1 id="network-hooks">
455
<title>NETWORK HOOKS</title>
457
If a network interface like a bridge or tunnel is required to
458
find a Mandos server, this requires the interface to be up and
459
running before <command>&COMMANDNAME;</command> starts looking
460
for Mandos servers. This can be accomplished by creating a
461
<quote>network hook</quote> program, and placing it in a special
465
Before the network is used (and again before program exit), any
466
runnable programs found in the network hook directory are run
467
with the argument <quote><literal>start</literal></quote> or
468
<quote><literal>stop</literal></quote>. This should bring up or
469
down, respectively, any network interface which
470
<command>&COMMANDNAME;</command> should use.
472
<refsect2 id="hook-requirements">
473
<title>REQUIREMENTS</title>
475
A network hook must be an executable file, and its name must
476
consist entirely of upper and lower case letters, digits,
477
underscores, periods, and hyphens.
480
A network hook will receive one argument, which can be one of
485
<term><literal>start</literal></term>
488
This should make the network hook create (if necessary)
489
and bring up a network interface.
494
<term><literal>stop</literal></term>
497
This should make the network hook take down a network
498
interface, and delete it if it did not exist previously.
503
<term><literal>files</literal></term>
506
This should make the network hook print, <emphasis>one
507
file per line</emphasis>, all the files needed for it to
508
run. (These files will be copied into the initial RAM
509
filesystem.) Typical use is for a network hook which is
510
a shell script to print its needed binaries.
513
It is not necessary to print any non-executable files
514
already in the network hook directory, these will be
515
copied implicitly if they otherwise satisfy the name
521
<term><literal>modules</literal></term>
524
This should make the network hook print, <emphasis>on
525
separate lines</emphasis>, all the kernel modules needed
526
for it to run. (These modules will be copied into the
527
initial RAM filesystem.) For instance, a tunnel
529
<quote><literal>tun</literal></quote> module.
535
The network hook will be provided with a number of environment
540
<term><envar>MANDOSNETHOOKDIR</envar></term>
543
The network hook directory, specified to
544
<command>&COMMANDNAME;</command> by the
545
<option>--network-hook-dir</option> option. Note: this
546
should <emphasis>always</emphasis> be used by the
547
network hook to refer to itself or any files in the hook
548
directory it may require.
553
<term><envar>DEVICE</envar></term>
556
The network interfaces, as specified to
557
<command>&COMMANDNAME;</command> by the
558
<option>--interface</option> option, combined to one
559
string and separated by commas. If this is set, and
560
does not contain the interface a hook will bring up,
561
there is no reason for a hook to continue.
566
<term><envar>MODE</envar></term>
569
This will be the same as the first argument;
570
i.e. <quote><literal>start</literal></quote>,
571
<quote><literal>stop</literal></quote>,
572
<quote><literal>files</literal></quote>, or
573
<quote><literal>modules</literal></quote>.
578
<term><envar>VERBOSITY</envar></term>
581
This will be the <quote><literal>1</literal></quote> if
582
the <option>--debug</option> option is passed to
583
<command>&COMMANDNAME;</command>, otherwise
584
<quote><literal>0</literal></quote>.
589
<term><envar>DELAY</envar></term>
592
This will be the same as the <option>--delay</option>
593
option passed to <command>&COMMANDNAME;</command>. Is
594
only set if <envar>MODE</envar> is
595
<quote><literal>start</literal></quote> or
596
<quote><literal>stop</literal></quote>.
601
<term><envar>CONNECT</envar></term>
604
This will be the same as the <option>--connect</option>
605
option passed to <command>&COMMANDNAME;</command>. Is
606
only set if <option>--connect</option> is passed and
607
<envar>MODE</envar> is
608
<quote><literal>start</literal></quote> or
609
<quote><literal>stop</literal></quote>.
615
A hook may not read from standard input, and should be
616
restrictive in printing to standard output or standard error
617
unless <varname>VERBOSITY</varname> is
618
<quote><literal>1</literal></quote>.
623
<refsect1 id="files">
624
241
<title>FILES</title>
627
<term><filename>/conf/conf.d/mandos/pubkey.txt</filename
629
<term><filename>/conf/conf.d/mandos/seckey.txt</filename
633
OpenPGP public and private key files, in <quote>ASCII
634
Armor</quote> format. These are the default file names,
635
they can be changed with the <option>--pubkey</option> and
636
<option>--seckey</option> options.
642
class="directory">/lib/mandos/network-hooks.d</filename></term>
645
Directory where network hooks are located. Change this
646
with the <option>--network-hook-dir</option> option. See
647
<xref linkend="network-hooks"/>.
654
<!-- <refsect1 id="bugs"> -->
655
<!-- <title>BUGS</title> -->
660
252
<refsect1 id="example">
661
253
<title>EXAMPLE</title>
663
Note that normally, command line options will not be given
664
directly, but via options for the Mandos <citerefentry
665
><refentrytitle>plugin-runner</refentrytitle>
666
<manvolnum>8mandos</manvolnum></citerefentry>.
670
Normal invocation needs no options, if the network interfaces
671
can be automatically determined:
674
<userinput>&COMMANDNAME;</userinput>
679
Search for Mandos servers (and connect to them) using one
683
<!-- do not wrap this line -->
684
<userinput>&COMMANDNAME; --interface eth1</userinput>
689
Run in debug mode, and use a custom key:
693
<!-- do not wrap this line -->
694
<userinput>&COMMANDNAME; --debug --pubkey keydir/pubkey.txt --seckey keydir/seckey.txt</userinput>
700
Run in debug mode, with a custom key, and do not use Zeroconf
701
to locate a server; connect directly to the IPv6 link-local
702
address <quote><systemitem class="ipaddress"
703
>fe80::aede:48ff:fe71:f6f2</systemitem></quote>, port 4711,
704
using interface eth2:
708
<!-- do not wrap this line -->
709
<userinput>&COMMANDNAME; --debug --pubkey keydir/pubkey.txt --seckey keydir/seckey.txt --connect fe80::aede:48ff:fe71:f6f2:4711 --interface eth2</userinput>
715
258
<refsect1 id="security">
716
259
<title>SECURITY</title>
718
This program is set-uid to root, but will switch back to the
719
original (and presumably non-privileged) user and group after
720
bringing up the network interface.
723
To use this program for its intended purpose (see <xref
724
linkend="purpose"/>), the password for the root file system will
725
have to be given out to be stored in a server computer, after
726
having been encrypted using an OpenPGP key. This encrypted data
727
which will be stored in a server can only be decrypted by the
728
OpenPGP key, and the data will only be given out to those
729
clients who can prove they actually have that key. This key,
730
however, is stored unencrypted on the client side in its initial
731
<acronym>RAM</acronym> disk image file system. This is normally
732
readable by all, but this is normally fixed during installation
733
of this program; file permissions are set so that no-one is able
737
The only remaining weak point is that someone with physical
738
access to the client hard drive might turn off the client
739
computer, read the OpenPGP keys directly from the hard drive,
740
and communicate with the server. To safeguard against this, the
741
server is supposed to notice the client disappearing and stop
742
giving out the encrypted data. Therefore, it is important to
743
set the timeout and checker interval values tightly on the
744
server. See <citerefentry><refentrytitle
745
>mandos</refentrytitle><manvolnum>8</manvolnum></citerefentry>.
748
It will also help if the checker program on the server is
749
configured to request something from the client which can not be
750
spoofed by someone else on the network, unlike unencrypted
751
<acronym>ICMP</acronym> echo (<quote>ping</quote>) replies.
754
<emphasis>Note</emphasis>: This makes it completely insecure to
755
have <application >Mandos</application> clients which dual-boot
756
to another operating system which is <emphasis>not</emphasis>
757
trusted to keep the initial <acronym>RAM</acronym> disk image
762
264
<refsect1 id="see_also">
763
265
<title>SEE ALSO</title>
765
<citerefentry><refentrytitle>intro</refentrytitle>
766
<manvolnum>8mandos</manvolnum></citerefentry>,
767
<citerefentry><refentrytitle>cryptsetup</refentrytitle>
768
<manvolnum>8</manvolnum></citerefentry>,
769
<citerefentry><refentrytitle>crypttab</refentrytitle>
770
<manvolnum>5</manvolnum></citerefentry>,
771
267
<citerefentry><refentrytitle>mandos</refentrytitle>
772
268
<manvolnum>8</manvolnum></citerefentry>,
773
269
<citerefentry><refentrytitle>password-prompt</refentrytitle>