99
<option>--delay <replaceable>SECONDS</replaceable></option>
103
<option>--retry <replaceable>SECONDS</replaceable></option>
107
<option>--network-hook-dir
108
<replaceable>DIR</replaceable></option>
112
124
<option>--debug</option>
116
128
<command>&COMMANDNAME;</command>
117
129
<group choice="req">
118
<arg choice="plain"><option>--help</option></arg>
119
<arg choice="plain"><option>-?</option></arg>
130
<arg choice='plain'><option>--help</option></arg>
131
<arg choice='plain'><option>-?</option></arg>
123
135
<command>&COMMANDNAME;</command>
124
<arg choice="plain"><option>--usage</option></arg>
136
<arg choice='plain'><option>--usage</option></arg>
127
139
<command>&COMMANDNAME;</command>
128
140
<group choice="req">
129
<arg choice="plain"><option>--version</option></arg>
130
<arg choice="plain"><option>-V</option></arg>
141
<arg choice='plain'><option>--version</option></arg>
142
<arg choice='plain'><option>-V</option></arg>
133
145
</refsynopsisdiv>
135
147
<refsect1 id="description">
136
148
<title>DESCRIPTION</title>
138
<command>&COMMANDNAME;</command> is a client program that
139
communicates with <citerefentry><refentrytitle
140
>mandos</refentrytitle><manvolnum>8</manvolnum></citerefentry>
141
to get a password. In slightly more detail, this client program
142
brings up network interfaces, uses the interfaces’ IPv6
143
link-local addresses to get network connectivity, uses Zeroconf
144
to find servers on the local network, and communicates with
145
servers using TLS with an OpenPGP key to ensure authenticity and
146
confidentiality. This client program keeps running, trying all
147
servers on the network, until it receives a satisfactory reply
148
or a TERM signal. After all servers have been tried, all
149
servers are periodically retried. If no servers are found it
150
will wait indefinitely for new servers to appear.
153
The network interfaces are selected like this: If any interfaces
154
are specified using the <option>--interface</option> option,
155
those interface are used. Otherwise,
156
<command>&COMMANDNAME;</command> will use all interfaces that
157
are not loopback interfaces, are not point-to-point interfaces,
158
are capable of broadcasting and do not have the NOARP flag (see
159
<citerefentry><refentrytitle>netdevice</refentrytitle>
160
<manvolnum>7</manvolnum></citerefentry>). (If the
161
<option>--connect</option> option is used, point-to-point
162
interfaces and non-broadcast interfaces are accepted.) If any
163
used interfaces are not up and running, they are first taken up
164
(and later taken down again on program exit).
167
Before network interfaces are selected, all <quote>network
168
hooks</quote> are run; see <xref linkend="network-hooks"/>.
171
This program is not meant to be run directly; it is really meant
172
to run as a plugin of the <application>Mandos</application>
173
<citerefentry><refentrytitle>plugin-runner</refentrytitle>
174
<manvolnum>8mandos</manvolnum></citerefentry>, which runs in the
175
initial <acronym>RAM</acronym> disk environment because it is
176
specified as a <quote>keyscript</quote> in the <citerefentry>
177
<refentrytitle>crypttab</refentrytitle><manvolnum>5</manvolnum>
178
</citerefentry> file.
182
<refsect1 id="purpose">
183
<title>PURPOSE</title>
185
The purpose of this is to enable <emphasis>remote and unattended
186
rebooting</emphasis> of client host computer with an
187
<emphasis>encrypted root file system</emphasis>. See <xref
188
linkend="overview"/> for details.
150
<command>&COMMANDNAME;</command> is a mandos plugin that works
151
like a client program that through avahi detects mandos servers,
152
sets up a gnutls connect and request a encrypted password. Any
153
passwords given is automaticly decrypted and passed to
192
158
<refsect1 id="options">
193
159
<title>OPTIONS</title>
195
This program is commonly not invoked from the command line; it
196
is normally started by the <application>Mandos</application>
197
plugin runner, see <citerefentry><refentrytitle
198
>plugin-runner</refentrytitle><manvolnum>8mandos</manvolnum>
199
</citerefentry>. Any command line options this program accepts
200
are therefore normally provided by the plugin runner, and not
161
Commonly not invoked as command lines but from configuration
162
file of plugin runner.
206
<term><option>--connect=<replaceable
207
>ADDRESS</replaceable><literal>:</literal><replaceable
208
>PORT</replaceable></option></term>
210
<replaceable>ADDRESS</replaceable><literal>:</literal
211
><replaceable>PORT</replaceable></option></term>
214
Do not use Zeroconf to locate servers. Connect directly
215
to only one specified <application>Mandos</application>
216
server. Note that an IPv6 address has colon characters in
217
it, so the <emphasis>last</emphasis> colon character is
218
assumed to separate the address from the port number.
221
This option is normally only useful for testing and
228
<term><option>--interface=<replaceable
229
>NAME</replaceable></option></term>
231
<replaceable>NAME</replaceable></option></term>
234
Comma separated list of network interfaces that will be
235
brought up and scanned for Mandos servers to connect to.
236
The default is the empty string, which will automatically
237
use all appropriate interfaces.
240
If the <option>--connect</option> option is used, this
241
specifies the interface to use to connect to the address
245
Note that since this program will normally run in the
246
initial RAM disk environment, the interface must be an
247
interface which exists at that stage. Thus, the interface
248
can normally not be a pseudo-interface such as
249
<quote>br0</quote> or <quote>tun0</quote>; such interfaces
250
will not exist until much later in the boot process, and
251
can not be used by this program, unless created by a
252
<quote>network hook</quote> — see <xref
253
linkend="network-hooks"/>.
256
<replaceable>NAME</replaceable> can be the string
257
<quote><literal>none</literal></quote>; this will not use
258
any specific interface, and will not bring up an interface
259
on startup. This is not recommended, and only meant for
266
<term><option>--pubkey=<replaceable
267
>FILE</replaceable></option></term>
269
<replaceable>FILE</replaceable></option></term>
272
OpenPGP public key file name. The default name is
273
<quote><filename>/conf/conf.d/mandos/pubkey.txt</filename
280
<term><option>--seckey=<replaceable
281
>FILE</replaceable></option></term>
283
<replaceable>FILE</replaceable></option></term>
286
OpenPGP secret key file name. The default name is
287
<quote><filename>/conf/conf.d/mandos/seckey.txt</filename
294
<term><option>--priority=<replaceable
295
>STRING</replaceable></option></term>
297
<xi:include href="../mandos-options.xml"
298
xpointer="priority"/>
303
<term><option>--dh-bits=<replaceable
304
>BITS</replaceable></option></term>
307
Sets the number of bits to use for the prime number in the
308
TLS Diffie-Hellman key exchange. Default is 1024.
314
<term><option>--delay=<replaceable
315
>SECONDS</replaceable></option></term>
318
After bringing a network interface up, the program waits
319
for the interface to arrive in a <quote>running</quote>
320
state before proceeding. During this time, the kernel log
321
level will be lowered to reduce clutter on the system
322
console, alleviating any other plugins which might be
323
using the system console. This option sets the upper
324
limit of seconds to wait. The default is 2.5 seconds.
330
<term><option>--retry=<replaceable
331
>SECONDS</replaceable></option></term>
334
All Mandos servers are tried repeatedly until a password
335
is received. This value specifies, in seconds, how long
336
between each successive try <emphasis>for the same
337
server</emphasis>. The default is 10 seconds.
343
<term><option>--network-hook-dir=<replaceable
344
>DIR</replaceable></option></term>
347
Network hook directory. The default directory is
348
<quote><filename class="directory"
349
>/lib/mandos/network-hooks.d</filename></quote>.
355
<term><option>--debug</option></term>
358
Enable debug mode. This will enable a lot of output to
359
standard error about what the program is doing. The
360
program will still perform all other functions normally.
363
It will also enable debug mode in the Avahi and GnuTLS
364
libraries, making them print large amounts of debugging
371
<term><option>--help</option></term>
372
<term><option>-?</option></term>
375
Gives a help message about options and their meanings.
381
<term><option>--usage</option></term>
384
Gives a short usage message.
390
<term><option>--version</option></term>
391
<term><option>-V</option></term>
394
Prints the program version.
167
<term><literal>-c</literal>, <literal>--connect=<replaceable>
168
IP</replaceable></literal></term>
171
Connect directly to a specified mandos server
177
<term><literal>-d</literal>, <literal>--keydir=<replaceable>
178
KEYDIR</replaceable></literal></term>
181
Directory where the openpgp keyring is
187
<term><literal>-i</literal>, <literal>--interface=
188
<replaceable>INTERFACE</replaceable></literal></term>
191
Interface that Avahi will conntect through
197
<term><literal>-p</literal>, <literal>--pubkey=<replaceable>
198
PUBKEY</replaceable></literal></term>
201
Public openpgp key for gnutls authentication
207
<term><literal>-s</literal>, <literal>--seckey=<replaceable>
208
SECKEY</replaceable></literal></term>
211
Secret openpgp key for gnutls authentication
217
<term><literal>--priority=<replaceable>PRIORITY</replaceable>
227
<term><literal>--dh-bits=<replaceable>BITS</replaceable>
231
dh-bits to use in gnutls communication
237
<term><literal>--debug</literal></term>
246
<term><literal>-?</literal>, <literal>--help</literal></term>
255
<term><literal>--usage</literal></term>
258
Gives a short usage message
264
<term><literal>-V</literal>, <literal>--version</literal></term>
267
Prints the program version
401
<refsect1 id="overview">
402
<title>OVERVIEW</title>
403
<xi:include href="../overview.xml"/>
405
This program is the client part. It is a plugin started by
406
<citerefentry><refentrytitle>plugin-runner</refentrytitle>
407
<manvolnum>8mandos</manvolnum></citerefentry> which will run in
408
an initial <acronym>RAM</acronym> disk environment.
411
This program could, theoretically, be used as a keyscript in
412
<filename>/etc/crypttab</filename>, but it would then be
413
impossible to enter a password for the encrypted root disk at
414
the console, since this program does not read from the console
415
at all. This is why a separate plugin runner (<citerefentry>
416
<refentrytitle>plugin-runner</refentrytitle>
417
<manvolnum>8mandos</manvolnum></citerefentry>) is used to run
418
both this program and others in in parallel,
419
<emphasis>one</emphasis> of which (<citerefentry>
420
<refentrytitle>password-prompt</refentrytitle>
421
<manvolnum>8mandos</manvolnum></citerefentry>) will prompt for
422
passwords on the system console.
426
274
<refsect1 id="exit_status">
427
275
<title>EXIT STATUS</title>
429
This program will exit with a successful (zero) exit status if a
430
server could be found and the password received from it could be
431
successfully decrypted and output on standard output. The
432
program will exit with a non-zero exit status only if a critical
433
error occurs. Otherwise, it will forever connect to any
434
discovered <application>Mandos</application> servers, trying to
435
get a decryptable password and print it.
439
280
<refsect1 id="environment">
440
281
<title>ENVIRONMENT</title>
442
This program does not use any environment variables, not even
443
the ones provided by <citerefentry><refentrytitle
444
>cryptsetup</refentrytitle><manvolnum>8</manvolnum>
449
<refsect1 id="network-hooks">
450
<title>NETWORK HOOKS</title>
452
If a network interface like a bridge or tunnel is required to
453
find a Mandos server, this requires the interface to be up and
454
running before <command>&COMMANDNAME;</command> starts looking
455
for Mandos servers. This can be accomplished by creating a
456
<quote>network hook</quote> program, and placing it in a special
460
Before the network is used (and again before program exit), any
461
runnable programs found in the network hook directory are run
462
with the argument <quote><literal>start</literal></quote> or
463
<quote><literal>stop</literal></quote>. This should bring up or
464
down, respectively, any network interface which
465
<command>&COMMANDNAME;</command> should use.
467
<refsect2 id="hook-requirements">
468
<title>REQUIREMENTS</title>
470
A network hook must be an executable file, and its name must
471
consist entirely of upper and lower case letters, digits,
472
underscores, periods, and hyphens.
475
A network hook will receive one argument, which can be one of
480
<term><literal>start</literal></term>
483
This should make the network hook create (if necessary)
484
and bring up a network interface.
489
<term><literal>stop</literal></term>
492
This should make the network hook take down a network
493
interface, and delete it if it did not exist previously.
498
<term><literal>files</literal></term>
501
This should make the network hook print, <emphasis>one
502
file per line</emphasis>, all the files needed for it to
503
run. (These files will be copied into the initial RAM
504
filesystem.) Typical use is for a network hook which is
505
a shell script to print its needed binaries.
508
It is not necessary to print any non-executable files
509
already in the network hook directory, these will be
510
copied implicitly if they otherwise satisfy the name
516
<term><literal>modules</literal></term>
519
This should make the network hook print, <emphasis>on
520
separate lines</emphasis>, all the kernel modules needed
521
for it to run. (These modules will be copied into the
522
initial RAM filesystem.) For instance, a tunnel
524
<quote><literal>tun</literal></quote> module.
530
The network hook will be provided with a number of environment
535
<term><envar>MANDOSNETHOOKDIR</envar></term>
538
The network hook directory, specified to
539
<command>&COMMANDNAME;</command> by the
540
<option>--network-hook-dir</option> option. Note: this
541
should <emphasis>always</emphasis> be used by the
542
network hook to refer to itself or any files in the hook
543
directory it may require.
548
<term><envar>DEVICE</envar></term>
551
The network interfaces, as specified to
552
<command>&COMMANDNAME;</command> by the
553
<option>--interface</option> option, combined to one
554
string and separated by commas. If this is set, and
555
does not contain the interface a hook will bring up,
556
there is no reason for a hook to continue.
561
<term><envar>MODE</envar></term>
564
This will be the same as the first argument;
565
i.e. <quote><literal>start</literal></quote>,
566
<quote><literal>stop</literal></quote>,
567
<quote><literal>files</literal></quote>, or
568
<quote><literal>modules</literal></quote>.
573
<term><envar>VERBOSITY</envar></term>
576
This will be the <quote><literal>1</literal></quote> if
577
the <option>--debug</option> option is passed to
578
<command>&COMMANDNAME;</command>, otherwise
579
<quote><literal>0</literal></quote>.
584
<term><envar>DELAY</envar></term>
587
This will be the same as the <option>--delay</option>
588
option passed to <command>&COMMANDNAME;</command>. Is
589
only set if <envar>MODE</envar> is
590
<quote><literal>start</literal></quote> or
591
<quote><literal>stop</literal></quote>.
596
<term><envar>CONNECT</envar></term>
599
This will be the same as the <option>--connect</option>
600
option passed to <command>&COMMANDNAME;</command>. Is
601
only set if <option>--connect</option> is passed and
602
<envar>MODE</envar> is
603
<quote><literal>start</literal></quote> or
604
<quote><literal>stop</literal></quote>.
610
A hook may not read from standard input, and should be
611
restrictive in printing to standard output or standard error
612
unless <varname>VERBOSITY</varname> is
613
<quote><literal>1</literal></quote>.
618
<refsect1 id="files">
619
287
<title>FILES</title>
622
<term><filename>/conf/conf.d/mandos/pubkey.txt</filename
624
<term><filename>/conf/conf.d/mandos/seckey.txt</filename
628
OpenPGP public and private key files, in <quote>ASCII
629
Armor</quote> format. These are the default file names,
630
they can be changed with the <option>--pubkey</option> and
631
<option>--seckey</option> options.
637
class="directory">/lib/mandos/network-hooks.d</filename></term>
640
Directory where network hooks are located. Change this
641
with the <option>--network-hook-dir</option> option. See
642
<xref linkend="network-hooks"/>.
649
<!-- <refsect1 id="bugs"> -->
650
<!-- <title>BUGS</title> -->
655
298
<refsect1 id="example">
656
299
<title>EXAMPLE</title>
658
Note that normally, command line options will not be given
659
directly, but via options for the Mandos <citerefentry
660
><refentrytitle>plugin-runner</refentrytitle>
661
<manvolnum>8mandos</manvolnum></citerefentry>.
665
Normal invocation needs no options, if the network interface
666
can be automatically determined:
669
<userinput>&COMMANDNAME;</userinput>
674
Search for Mandos servers (and connect to them) using another
678
<!-- do not wrap this line -->
679
<userinput>&COMMANDNAME; --interface eth1</userinput>
684
Run in debug mode, and use a custom key:
688
<!-- do not wrap this line -->
689
<userinput>&COMMANDNAME; --debug --pubkey keydir/pubkey.txt --seckey keydir/seckey.txt</userinput>
695
Run in debug mode, with a custom key, and do not use Zeroconf
696
to locate a server; connect directly to the IPv6 link-local
697
address <quote><systemitem class="ipaddress"
698
>fe80::aede:48ff:fe71:f6f2</systemitem></quote>, port 4711,
699
using interface eth2:
703
<!-- do not wrap this line -->
704
<userinput>&COMMANDNAME; --debug --pubkey keydir/pubkey.txt --seckey keydir/seckey.txt --connect fe80::aede:48ff:fe71:f6f2:4711 --interface eth2</userinput>
710
304
<refsect1 id="security">
711
305
<title>SECURITY</title>
713
This program is set-uid to root, but will switch back to the
714
original (and presumably non-privileged) user and group after
715
bringing up the network interface.
718
To use this program for its intended purpose (see <xref
719
linkend="purpose"/>), the password for the root file system will
720
have to be given out to be stored in a server computer, after
721
having been encrypted using an OpenPGP key. This encrypted data
722
which will be stored in a server can only be decrypted by the
723
OpenPGP key, and the data will only be given out to those
724
clients who can prove they actually have that key. This key,
725
however, is stored unencrypted on the client side in its initial
726
<acronym>RAM</acronym> disk image file system. This is normally
727
readable by all, but this is normally fixed during installation
728
of this program; file permissions are set so that no-one is able
732
The only remaining weak point is that someone with physical
733
access to the client hard drive might turn off the client
734
computer, read the OpenPGP keys directly from the hard drive,
735
and communicate with the server. To safeguard against this, the
736
server is supposed to notice the client disappearing and stop
737
giving out the encrypted data. Therefore, it is important to
738
set the timeout and checker interval values tightly on the
739
server. See <citerefentry><refentrytitle
740
>mandos</refentrytitle><manvolnum>8</manvolnum></citerefentry>.
743
It will also help if the checker program on the server is
744
configured to request something from the client which can not be
745
spoofed by someone else on the network, unlike unencrypted
746
<acronym>ICMP</acronym> echo (<quote>ping</quote>) replies.
749
<emphasis>Note</emphasis>: This makes it completely insecure to
750
have <application >Mandos</application> clients which dual-boot
751
to another operating system which is <emphasis>not</emphasis>
752
trusted to keep the initial <acronym>RAM</acronym> disk image
757
310
<refsect1 id="see_also">
758
311
<title>SEE ALSO</title>
760
<citerefentry><refentrytitle>intro</refentrytitle>
761
<manvolnum>8mandos</manvolnum></citerefentry>,
762
<citerefentry><refentrytitle>cryptsetup</refentrytitle>
763
<manvolnum>8</manvolnum></citerefentry>,
764
<citerefentry><refentrytitle>crypttab</refentrytitle>
765
<manvolnum>5</manvolnum></citerefentry>,
766
313
<citerefentry><refentrytitle>mandos</refentrytitle>
767
314
<manvolnum>8</manvolnum></citerefentry>,
768
315
<citerefentry><refentrytitle>password-prompt</refentrytitle>