11
12
<title>Mandos Manual</title>
12
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>
18
19
<firstname>Björn</firstname>
19
20
<surname>Påhlsson</surname>
21
<email>belorn@fukt.bsnet.se</email>
22
<email>belorn@recompile.se</email>
25
26
<firstname>Teddy</firstname>
26
27
<surname>Hogeborn</surname>
28
<email>teddy@fukt.bsnet.se</email>
29
<email>teddy@recompile.se</email>
34
43
<holder>Teddy Hogeborn</holder>
35
44
<holder>Björn Påhlsson</holder>
37
46
<xi:include href="legalnotice.xml"/>
41
50
<refentrytitle>&COMMANDNAME;</refentrytitle>
42
51
<manvolnum>8mandos</manvolnum>
46
55
<refname><command>&COMMANDNAME;</command></refname>
48
Run Mandos plugins. Pass data from first succesful one.
57
Run Mandos plugins, pass data from first to succeed.
54
63
<command>&COMMANDNAME;</command>
55
64
<group rep="repeat">
56
65
<arg choice="plain"><option>--global-env=<replaceable
57
>VAR</replaceable><literal>=</literal><replaceable
66
>ENV</replaceable><literal>=</literal><replaceable
58
67
>value</replaceable></option></arg>
59
<arg choice="plain"><option>-e
60
<replaceable>VAR</replaceable><literal>=</literal><replaceable
68
<arg choice="plain"><option>-G
69
<replaceable>ENV</replaceable><literal>=</literal><replaceable
61
70
>value</replaceable> </option></arg>
130
152
<title>DESCRIPTION</title>
132
154
<command>&COMMANDNAME;</command> is a program which is meant to
133
be specified as <quote>keyscript</quote> in <citerefentry>
134
<refentrytitle>crypttab</refentrytitle>
135
<manvolnum>5</manvolnum></citerefentry> for the root disk. The
136
aim of this program is therefore to output a password, which
137
then <citerefentry><refentrytitle>cryptsetup</refentrytitle>
138
<manvolnum>8</manvolnum></citerefentry> will use to try and
139
unlock the root disk.
155
be specified as a <quote>keyscript</quote> for the root disk in
156
<citerefentry><refentrytitle>crypttab</refentrytitle>
157
<manvolnum>5</manvolnum></citerefentry>. The aim of this
158
program is therefore to output a password, which then
159
<citerefentry><refentrytitle>cryptsetup</refentrytitle>
160
<manvolnum>8</manvolnum></citerefentry> will use to unlock the
142
164
This program is not meant to be invoked directly, but can be in
231
253
<option>--bar</option> with the option argument
232
254
<quote>baz</quote> is either
233
255
<userinput>--options-for=foo:--bar=baz</userinput> or
234
<userinput>--options-for=foo:--bar,baz</userinput>, but
235
<emphasis>not</emphasis>
236
<userinput>--options-for="foo:--bar baz"</userinput>.
256
<userinput>--options-for=foo:--bar,baz</userinput>. Using
257
<userinput>--options-for="foo:--bar baz"</userinput>. will
258
<emphasis>not</emphasis> work.
242
<term><option> --disable
264
<term><option>--disable
243
265
<replaceable>PLUGIN</replaceable></option></term>
245
267
<replaceable>PLUGIN</replaceable></option></term>
332
<term><option>--plugin-helper-dir
333
<replaceable>DIRECTORY</replaceable></option></term>
336
Specify a different plugin helper directory. The default
337
is <filename>/lib/mandos/plugin-helpers</filename>, which
338
will exist in the initial <acronym>RAM</acronym> disk
339
environment. (This will simply be passed to all plugins
340
via the <envar>MANDOSPLUGINHELPERDIR</envar> environment
341
variable. See <xref linkend="writing_plugins"/>)
347
<term><option>--config-file
348
<replaceable>FILE</replaceable></option></term>
351
Specify a different file to read additional options from.
352
See <xref linkend="files"/>. Other command line options
353
will override options specified in the file.
295
359
<term><option>--debug</option></term>
366
430
code will make this plugin-runner output the password from that
367
431
plugin, stop any other plugins, and exit.
434
<refsect2 id="writing_plugins">
435
<title>WRITING PLUGINS</title>
437
A plugin is simply a program which prints a password to its
438
standard output and then exits with a successful (zero) exit
439
status. If the exit status is not zero, any output on
440
standard output will be ignored by the plugin runner. Any
441
output on its standard error channel will simply be passed to
442
the standard error of the plugin runner, usually the system
446
If the password is a single-line, manually entered passprase,
447
a final trailing newline character should
448
<emphasis>not</emphasis> be printed.
451
The plugin will run in the initial RAM disk environment, so
452
care must be taken not to depend on any files or running
453
services not available there. Any helper executables required
454
by the plugin (which are not in the <envar>PATH</envar>) can
455
be placed in the plugin helper directory, the name of which
456
will be made available to the plugin via the
457
<envar>MANDOSPLUGINHELPERDIR</envar> environment variable.
460
The plugin must exit cleanly and free all allocated resources
461
upon getting the TERM signal, since this is what the plugin
462
runner uses to stop all other plugins when one plugin has
463
output a password and exited cleanly.
466
The plugin must not use resources, like for instance reading
467
from the standard input, without knowing that no other plugin
471
It is useful, but not required, for the plugin to take the
472
<option>--debug</option> option.
371
477
<refsect1 id="fallback">
415
527
of a line is ignored.
530
This program is meant to run in the initial RAM disk
531
environment, so that is where this file is assumed to
532
exist. The file does not need to exist in the normal
418
536
This file will be processed <emphasis>before</emphasis>
419
537
the normal command line options, so the latter can
420
538
override the former, if need be.
541
This file name is the default; the file to read for
542
arguments can be changed using the
543
<option>--config-file</option> option.
548
<term><filename class="directory"
549
>/lib/mandos/plugins.d</filename></term>
552
The default plugin directory; can be changed by the
553
<option>--plugin-dir</option> option.
558
<term><filename class="directory"
559
>/lib/mandos/plugin-helpers</filename></term>
562
The default plugin helper directory; can be changed by
563
the <option>--plugin-helper-dir</option> option.
428
571
<refsect1 id="bugs">
429
572
<title>BUGS</title>
431
There is no <option>--enable</option> option to enable disabled
574
The <option>--config-file</option> option is ignored when
575
specified from within a configuration file.
577
<xi:include href="bugs.xml"/>
436
580
<refsect1 id="examples">
437
581
<title>EXAMPLE</title>
584
Normal invocation needs no options:
587
<userinput>&COMMANDNAME;</userinput>
592
Run the program, but not the plugins, in debug mode:
596
<!-- do not wrap this line -->
597
<userinput>&COMMANDNAME; --debug</userinput>
603
Run all plugins, but run the <quote>foo</quote> plugin in
608
<!-- do not wrap this line -->
609
<userinput>&COMMANDNAME; --options-for=foo:--debug</userinput>
615
Run all plugins, but not the program, in debug mode:
619
<!-- do not wrap this line -->
620
<userinput>&COMMANDNAME; --global-options=--debug</userinput>
626
Read a different configuration file, run plugins from a
627
different directory, specify an alternate plugin helper
628
directory and add two options to the
629
<citerefentry><refentrytitle >mandos-client</refentrytitle>
630
<manvolnum>8mandos</manvolnum></citerefentry> plugin:
634
<!-- do not wrap this line -->
635
<userinput>cd /etc/keys/mandos; &COMMANDNAME; --config-file=/etc/mandos/plugin-runner.conf --plugin-dir /usr/lib/x86_64-linux-gnu/mandos/plugins.d --plugin-helper-dir /usr/lib/x86_64-linux-gnu/mandos/plugin-helpers --options-for=mandos-client:--pubkey=pubkey.txt,--seckey=seckey.txt</userinput>
442
640
<refsect1 id="security">
443
641
<title>SECURITY</title>
643
This program will, when starting, try to switch to another user.
644
If it is started as root, it will succeed, and will by default
645
switch to user and group 65534, which are assumed to be
646
non-privileged. This user and group is then what all plugins
647
will be started as. Therefore, the only way to run a plugin as
648
a privileged user is to have the set-user-ID or set-group-ID bit
649
set on the plugin executable file (see <citerefentry>
650
<refentrytitle>execve</refentrytitle><manvolnum>2</manvolnum>
654
If this program is used as a keyscript in <citerefentry
655
><refentrytitle>crypttab</refentrytitle><manvolnum>5</manvolnum>
656
</citerefentry>, there is a slight risk that if this program
657
fails to work, there might be no way to boot the system except
658
for booting from another media and editing the initial RAM disk
659
image to not run this program. This is, however, unlikely,
660
since the <citerefentry><refentrytitle
661
>password-prompt</refentrytitle><manvolnum>8mandos</manvolnum>
662
</citerefentry> plugin will read a password from the console in
663
case of failure of the other plugins, and this plugin runner
664
will also, in case of catastrophic failure, itself fall back to
665
asking and outputting a password on the console (see <xref
666
linkend="fallback"/>).
448
670
<refsect1 id="see_also">
449
671
<title>SEE ALSO</title>
673
<citerefentry><refentrytitle>intro</refentrytitle>
674
<manvolnum>8mandos</manvolnum></citerefentry>,
451
675
<citerefentry><refentrytitle>cryptsetup</refentrytitle>
452
676
<manvolnum>8</manvolnum></citerefentry>,
677
<citerefentry><refentrytitle>crypttab</refentrytitle>
678
<manvolnum>5</manvolnum></citerefentry>,
679
<citerefentry><refentrytitle>execve</refentrytitle>
680
<manvolnum>2</manvolnum></citerefentry>,
453
681
<citerefentry><refentrytitle>mandos</refentrytitle>
454
682
<manvolnum>8</manvolnum></citerefentry>,
455
683
<citerefentry><refentrytitle>password-prompt</refentrytitle>
456
684
<manvolnum>8mandos</manvolnum></citerefentry>,
457
<citerefentry><refentrytitle>password-request</refentrytitle>
685
<citerefentry><refentrytitle>mandos-client</refentrytitle>
458
686
<manvolnum>8mandos</manvolnum></citerefentry>