69
54
<refname><command>&COMMANDNAME;</command></refname>
56
Client for <application>Mandos</application>
77
62
<command>&COMMANDNAME;</command>
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>
64
<arg choice="plain"><option>--connect
65
<replaceable>ADDRESS</replaceable><literal>:</literal
66
><replaceable>PORT</replaceable></option></arg>
67
<arg choice="plain"><option>-c
68
<replaceable>ADDRESS</replaceable><literal>:</literal
69
><replaceable>PORT</replaceable></option></arg>
73
<arg choice="plain"><option>--interface
74
<replaceable>NAME</replaceable><arg rep='repeat'
75
>,<replaceable>NAME</replaceable></arg></option></arg>
76
<arg choice="plain"><option>-i <replaceable>NAME</replaceable
77
><arg rep='repeat'>,<replaceable>NAME</replaceable></arg
82
<arg choice="plain"><option>--pubkey
83
<replaceable>FILE</replaceable></option></arg>
84
<arg choice="plain"><option>-p
85
<replaceable>FILE</replaceable></option></arg>
89
<arg choice="plain"><option>--seckey
90
<replaceable>FILE</replaceable></option></arg>
91
<arg choice="plain"><option>-s
92
<replaceable>FILE</replaceable></option></arg>
96
<option>--priority <replaceable>STRING</replaceable></option>
100
<option>--dh-bits <replaceable>BITS</replaceable></option>
104
<option>--dh-params <replaceable>FILE</replaceable></option>
108
<option>--delay <replaceable>SECONDS</replaceable></option>
112
<option>--retry <replaceable>SECONDS</replaceable></option>
116
<option>--network-hook-dir
117
<replaceable>DIR</replaceable></option>
121
<option>--debug</option>
125
<command>&COMMANDNAME;</command>
127
<arg choice="plain"><option>--help</option></arg>
128
<arg choice="plain"><option>-?</option></arg>
132
<command>&COMMANDNAME;</command>
133
<arg choice="plain"><option>--usage</option></arg>
136
<command>&COMMANDNAME;</command>
138
<arg choice="plain"><option>--version</option></arg>
139
<arg choice="plain"><option>-V</option></arg>
101
144
<refsect1 id="description">
102
145
<title>DESCRIPTION</title>
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
147
<command>&COMMANDNAME;</command> is a client program that
148
communicates with <citerefentry><refentrytitle
149
>mandos</refentrytitle><manvolnum>8</manvolnum></citerefentry>
150
to get a password. In slightly more detail, this client program
151
brings up network interfaces, uses the interfaces’ IPv6
152
link-local addresses to get network connectivity, uses Zeroconf
153
to find servers on the local network, and communicates with
154
servers using TLS with an OpenPGP key to ensure authenticity and
155
confidentiality. This client program keeps running, trying all
156
servers on the network, until it receives a satisfactory reply
157
or a TERM signal. After all servers have been tried, all
158
servers are periodically retried. If no servers are found it
159
will wait indefinitely for new servers to appear.
162
The network interfaces are selected like this: If any interfaces
163
are specified using the <option>--interface</option> option,
164
those interface are used. Otherwise,
165
<command>&COMMANDNAME;</command> will use all interfaces that
166
are not loopback interfaces, are not point-to-point interfaces,
167
are capable of broadcasting and do not have the NOARP flag (see
168
<citerefentry><refentrytitle>netdevice</refentrytitle>
169
<manvolnum>7</manvolnum></citerefentry>). (If the
170
<option>--connect</option> option is used, point-to-point
171
interfaces and non-broadcast interfaces are accepted.) If any
172
used interfaces are not up and running, they are first taken up
173
(and later taken down again on program exit).
176
Before network interfaces are selected, all <quote>network
177
hooks</quote> are run; see <xref linkend="network-hooks"/>.
180
This program is not meant to be run directly; it is really meant
181
to run as a plugin of the <application>Mandos</application>
182
<citerefentry><refentrytitle>plugin-runner</refentrytitle>
183
<manvolnum>8mandos</manvolnum></citerefentry>, which runs in the
184
initial <acronym>RAM</acronym> disk environment because it is
185
specified as a <quote>keyscript</quote> in the <citerefentry>
186
<refentrytitle>crypttab</refentrytitle><manvolnum>5</manvolnum>
187
</citerefentry> file.
191
<refsect1 id="purpose">
192
<title>PURPOSE</title>
194
The purpose of this is to enable <emphasis>remote and unattended
195
rebooting</emphasis> of client host computer with an
196
<emphasis>encrypted root file system</emphasis>. See <xref
197
linkend="overview"/> for details.
112
201
<refsect1 id="options">
113
202
<title>OPTIONS</title>
115
Commonly not invoked as command lines but from configuration
116
file of plugin runner.
204
This program is commonly not invoked from the command line; it
205
is normally started by the <application>Mandos</application>
206
plugin runner, see <citerefentry><refentrytitle
207
>plugin-runner</refentrytitle><manvolnum>8mandos</manvolnum>
208
</citerefentry>. Any command line options this program accepts
209
are therefore normally provided by the plugin runner, and not
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
215
<term><option>--connect=<replaceable
216
>ADDRESS</replaceable><literal>:</literal><replaceable
217
>PORT</replaceable></option></term>
219
<replaceable>ADDRESS</replaceable><literal>:</literal
220
><replaceable>PORT</replaceable></option></term>
223
Do not use Zeroconf to locate servers. Connect directly
224
to only one specified <application>Mandos</application>
225
server. Note that an IPv6 address has colon characters in
226
it, so the <emphasis>last</emphasis> colon character is
227
assumed to separate the address from the port number.
230
Normally, Zeroconf would be used to locate Mandos servers,
231
in which case this option would only be used when testing
238
<term><option>--interface=<replaceable
239
>NAME</replaceable><arg rep='repeat'>,<replaceable
240
>NAME</replaceable></arg></option></term>
242
<replaceable>NAME</replaceable><arg rep='repeat'>,<replaceable
243
>NAME</replaceable></arg></option></term>
246
Comma separated list of network interfaces that will be
247
brought up and scanned for Mandos servers to connect to.
248
The default is the empty string, which will automatically
249
use all appropriate interfaces.
252
If the <option>--connect</option> option is used, and
253
exactly one interface name is specified (except
254
<quote><literal>none</literal></quote>), this specifies
255
the interface to use to connect to the address given.
258
Note that since this program will normally run in the
259
initial RAM disk environment, the interface must be an
260
interface which exists at that stage. Thus, the interface
261
can normally not be a pseudo-interface such as
262
<quote>br0</quote> or <quote>tun0</quote>; such interfaces
263
will not exist until much later in the boot process, and
264
can not be used by this program, unless created by a
265
<quote>network hook</quote> — see <xref
266
linkend="network-hooks"/>.
269
<replaceable>NAME</replaceable> can be the string
270
<quote><literal>none</literal></quote>; this will make
271
<command>&COMMANDNAME;</command> only bring up interfaces
272
specified <emphasis>before</emphasis> this string. This
273
is not recommended, and only meant for advanced users.
279
<term><option>--pubkey=<replaceable
280
>FILE</replaceable></option></term>
282
<replaceable>FILE</replaceable></option></term>
285
OpenPGP public key file name. The default name is
286
<quote><filename>/conf/conf.d/mandos/pubkey.txt</filename
293
<term><option>--seckey=<replaceable
294
>FILE</replaceable></option></term>
296
<replaceable>FILE</replaceable></option></term>
299
OpenPGP secret key file name. The default name is
300
<quote><filename>/conf/conf.d/mandos/seckey.txt</filename
307
<term><option>--priority=<replaceable
308
>STRING</replaceable></option></term>
310
<xi:include href="../mandos-options.xml"
311
xpointer="priority"/>
316
<term><option>--dh-bits=<replaceable
317
>BITS</replaceable></option></term>
320
Sets the number of bits to use for the prime number in the
321
TLS Diffie-Hellman key exchange. The default value is
322
selected automatically based on the OpenPGP key. Note
323
that if the <option>--dh-params</option> option is used,
324
the values from that file will be used instead.
330
<term><option>--dh-params=<replaceable
331
>FILE</replaceable></option></term>
334
Specifies a PEM-encoded PKCS#3 file to read the parameters
335
needed by the TLS Diffie-Hellman key exchange from. If
336
this option is not given, or if the file for some reason
337
could not be used, the parameters will be generated on
338
startup, which will take some time and processing power.
339
Those using servers running under time, power or processor
340
constraints may want to generate such a file in advance
347
<term><option>--delay=<replaceable
348
>SECONDS</replaceable></option></term>
351
After bringing a network interface up, the program waits
352
for the interface to arrive in a <quote>running</quote>
353
state before proceeding. During this time, the kernel log
354
level will be lowered to reduce clutter on the system
355
console, alleviating any other plugins which might be
356
using the system console. This option sets the upper
357
limit of seconds to wait. The default is 2.5 seconds.
363
<term><option>--retry=<replaceable
364
>SECONDS</replaceable></option></term>
367
All Mandos servers are tried repeatedly until a password
368
is received. This value specifies, in seconds, how long
369
between each successive try <emphasis>for the same
370
server</emphasis>. The default is 10 seconds.
376
<term><option>--network-hook-dir=<replaceable
377
>DIR</replaceable></option></term>
380
Network hook directory. The default directory is
381
<quote><filename class="directory"
382
>/lib/mandos/network-hooks.d</filename></quote>.
388
<term><option>--debug</option></term>
391
Enable debug mode. This will enable a lot of output to
392
standard error about what the program is doing. The
393
program will still perform all other functions normally.
396
It will also enable debug mode in the Avahi and GnuTLS
397
libraries, making them print large amounts of debugging
404
<term><option>--help</option></term>
405
<term><option>-?</option></term>
408
Gives a help message about options and their meanings.
414
<term><option>--usage</option></term>
417
Gives a short usage message.
423
<term><option>--version</option></term>
424
<term><option>-V</option></term>
427
Prints the program version.
434
<refsect1 id="overview">
435
<title>OVERVIEW</title>
436
<xi:include href="../overview.xml"/>
438
This program is the client part. It is a plugin started by
439
<citerefentry><refentrytitle>plugin-runner</refentrytitle>
440
<manvolnum>8mandos</manvolnum></citerefentry> which will run in
441
an initial <acronym>RAM</acronym> disk environment.
444
This program could, theoretically, be used as a keyscript in
445
<filename>/etc/crypttab</filename>, but it would then be
446
impossible to enter a password for the encrypted root disk at
447
the console, since this program does not read from the console
448
at all. This is why a separate plugin runner (<citerefentry>
449
<refentrytitle>plugin-runner</refentrytitle>
450
<manvolnum>8mandos</manvolnum></citerefentry>) is used to run
451
both this program and others in in parallel,
452
<emphasis>one</emphasis> of which (<citerefentry>
453
<refentrytitle>password-prompt</refentrytitle>
454
<manvolnum>8mandos</manvolnum></citerefentry>) will prompt for
455
passwords on the system console.
228
459
<refsect1 id="exit_status">
229
460
<title>EXIT STATUS</title>
462
This program will exit with a successful (zero) exit status if a
463
server could be found and the password received from it could be
464
successfully decrypted and output on standard output. The
465
program will exit with a non-zero exit status only if a critical
466
error occurs. Otherwise, it will forever connect to any
467
discovered <application>Mandos</application> servers, trying to
468
get a decryptable password and print it.
234
472
<refsect1 id="environment">
235
473
<title>ENVIRONMENT</title>
476
<term><envar>MANDOSPLUGINHELPERDIR</envar></term>
479
This environment variable will be assumed to contain the
480
directory containing any helper executables. The use and
481
nature of these helper executables, if any, is
482
purposefully not documented.
488
This program does not use any other environment variables, not
489
even the ones provided by <citerefentry><refentrytitle
490
>cryptsetup</refentrytitle><manvolnum>8</manvolnum>
495
<refsect1 id="network-hooks">
496
<title>NETWORK HOOKS</title>
498
If a network interface like a bridge or tunnel is required to
499
find a Mandos server, this requires the interface to be up and
500
running before <command>&COMMANDNAME;</command> starts looking
501
for Mandos servers. This can be accomplished by creating a
502
<quote>network hook</quote> program, and placing it in a special
506
Before the network is used (and again before program exit), any
507
runnable programs found in the network hook directory are run
508
with the argument <quote><literal>start</literal></quote> or
509
<quote><literal>stop</literal></quote>. This should bring up or
510
down, respectively, any network interface which
511
<command>&COMMANDNAME;</command> should use.
513
<refsect2 id="hook-requirements">
514
<title>REQUIREMENTS</title>
516
A network hook must be an executable file, and its name must
517
consist entirely of upper and lower case letters, digits,
518
underscores, periods, and hyphens.
521
A network hook will receive one argument, which can be one of
526
<term><literal>start</literal></term>
529
This should make the network hook create (if necessary)
530
and bring up a network interface.
535
<term><literal>stop</literal></term>
538
This should make the network hook take down a network
539
interface, and delete it if it did not exist previously.
544
<term><literal>files</literal></term>
547
This should make the network hook print, <emphasis>one
548
file per line</emphasis>, all the files needed for it to
549
run. (These files will be copied into the initial RAM
550
filesystem.) Typical use is for a network hook which is
551
a shell script to print its needed binaries.
554
It is not necessary to print any non-executable files
555
already in the network hook directory, these will be
556
copied implicitly if they otherwise satisfy the name
562
<term><literal>modules</literal></term>
565
This should make the network hook print, <emphasis>on
566
separate lines</emphasis>, all the kernel modules needed
567
for it to run. (These modules will be copied into the
568
initial RAM filesystem.) For instance, a tunnel
570
<quote><literal>tun</literal></quote> module.
576
The network hook will be provided with a number of environment
581
<term><envar>MANDOSNETHOOKDIR</envar></term>
584
The network hook directory, specified to
585
<command>&COMMANDNAME;</command> by the
586
<option>--network-hook-dir</option> option. Note: this
587
should <emphasis>always</emphasis> be used by the
588
network hook to refer to itself or any files in the hook
589
directory it may require.
594
<term><envar>DEVICE</envar></term>
597
The network interfaces, as specified to
598
<command>&COMMANDNAME;</command> by the
599
<option>--interface</option> option, combined to one
600
string and separated by commas. If this is set, and
601
does not contain the interface a hook will bring up,
602
there is no reason for a hook to continue.
607
<term><envar>MODE</envar></term>
610
This will be the same as the first argument;
611
i.e. <quote><literal>start</literal></quote>,
612
<quote><literal>stop</literal></quote>,
613
<quote><literal>files</literal></quote>, or
614
<quote><literal>modules</literal></quote>.
619
<term><envar>VERBOSITY</envar></term>
622
This will be the <quote><literal>1</literal></quote> if
623
the <option>--debug</option> option is passed to
624
<command>&COMMANDNAME;</command>, otherwise
625
<quote><literal>0</literal></quote>.
630
<term><envar>DELAY</envar></term>
633
This will be the same as the <option>--delay</option>
634
option passed to <command>&COMMANDNAME;</command>. Is
635
only set if <envar>MODE</envar> is
636
<quote><literal>start</literal></quote> or
637
<quote><literal>stop</literal></quote>.
642
<term><envar>CONNECT</envar></term>
645
This will be the same as the <option>--connect</option>
646
option passed to <command>&COMMANDNAME;</command>. Is
647
only set if <option>--connect</option> is passed and
648
<envar>MODE</envar> is
649
<quote><literal>start</literal></quote> or
650
<quote><literal>stop</literal></quote>.
656
A hook may not read from standard input, and should be
657
restrictive in printing to standard output or standard error
658
unless <varname>VERBOSITY</varname> is
659
<quote><literal>1</literal></quote>.
664
<refsect1 id="files">
241
665
<title>FILES</title>
668
<term><filename>/conf/conf.d/mandos/pubkey.txt</filename
670
<term><filename>/conf/conf.d/mandos/seckey.txt</filename
674
OpenPGP public and private key files, in <quote>ASCII
675
Armor</quote> format. These are the default file names,
676
they can be changed with the <option>--pubkey</option> and
677
<option>--seckey</option> options.
683
class="directory">/lib/mandos/network-hooks.d</filename></term>
686
Directory where network hooks are located. Change this
687
with the <option>--network-hook-dir</option> option. See
688
<xref linkend="network-hooks"/>.
695
<!-- <refsect1 id="bugs"> -->
696
<!-- <title>BUGS</title> -->
252
701
<refsect1 id="example">
253
702
<title>EXAMPLE</title>
704
Note that normally, command line options will not be given
705
directly, but via options for the Mandos <citerefentry
706
><refentrytitle>plugin-runner</refentrytitle>
707
<manvolnum>8mandos</manvolnum></citerefentry>.
711
Normal invocation needs no options, if the network interfaces
712
can be automatically determined:
715
<userinput>&COMMANDNAME;</userinput>
720
Search for Mandos servers (and connect to them) using one
724
<!-- do not wrap this line -->
725
<userinput>&COMMANDNAME; --interface eth1</userinput>
730
Run in debug mode, and use a custom key:
734
<!-- do not wrap this line -->
735
<userinput>&COMMANDNAME; --debug --pubkey keydir/pubkey.txt --seckey keydir/seckey.txt</userinput>
741
Run in debug mode, with a custom key, and do not use Zeroconf
742
to locate a server; connect directly to the IPv6 link-local
743
address <quote><systemitem class="ipaddress"
744
>fe80::aede:48ff:fe71:f6f2</systemitem></quote>, port 4711,
745
using interface eth2:
749
<!-- do not wrap this line -->
750
<userinput>&COMMANDNAME; --debug --pubkey keydir/pubkey.txt --seckey keydir/seckey.txt --connect fe80::aede:48ff:fe71:f6f2:4711 --interface eth2</userinput>
258
756
<refsect1 id="security">
259
757
<title>SECURITY</title>
759
This program is set-uid to root, but will switch back to the
760
original (and presumably non-privileged) user and group after
761
bringing up the network interface.
764
To use this program for its intended purpose (see <xref
765
linkend="purpose"/>), the password for the root file system will
766
have to be given out to be stored in a server computer, after
767
having been encrypted using an OpenPGP key. This encrypted data
768
which will be stored in a server can only be decrypted by the
769
OpenPGP key, and the data will only be given out to those
770
clients who can prove they actually have that key. This key,
771
however, is stored unencrypted on the client side in its initial
772
<acronym>RAM</acronym> disk image file system. This is normally
773
readable by all, but this is normally fixed during installation
774
of this program; file permissions are set so that no-one is able
778
The only remaining weak point is that someone with physical
779
access to the client hard drive might turn off the client
780
computer, read the OpenPGP keys directly from the hard drive,
781
and communicate with the server. To safeguard against this, the
782
server is supposed to notice the client disappearing and stop
783
giving out the encrypted data. Therefore, it is important to
784
set the timeout and checker interval values tightly on the
785
server. See <citerefentry><refentrytitle
786
>mandos</refentrytitle><manvolnum>8</manvolnum></citerefentry>.
789
It will also help if the checker program on the server is
790
configured to request something from the client which can not be
791
spoofed by someone else on the network, like SSH server key
792
fingerprints, and unlike unencrypted <acronym>ICMP</acronym>
793
echo (<quote>ping</quote>) replies.
796
<emphasis>Note</emphasis>: This makes it completely insecure to
797
have <application >Mandos</application> clients which dual-boot
798
to another operating system which is <emphasis>not</emphasis>
799
trusted to keep the initial <acronym>RAM</acronym> disk image
264
804
<refsect1 id="see_also">
265
805
<title>SEE ALSO</title>
807
<citerefentry><refentrytitle>intro</refentrytitle>
808
<manvolnum>8mandos</manvolnum></citerefentry>,
809
<citerefentry><refentrytitle>cryptsetup</refentrytitle>
810
<manvolnum>8</manvolnum></citerefentry>,
811
<citerefentry><refentrytitle>crypttab</refentrytitle>
812
<manvolnum>5</manvolnum></citerefentry>,
267
813
<citerefentry><refentrytitle>mandos</refentrytitle>
268
814
<manvolnum>8</manvolnum></citerefentry>,
269
815
<citerefentry><refentrytitle>password-prompt</refentrytitle>