12
11
<title>Mandos Manual</title>
13
12
<!-- Nwalsh’s docbook scripts use this to generate the footer: -->
14
13
<productname>Mandos</productname>
15
<productnumber>&version;</productnumber>
14
<productnumber>&VERSION;</productnumber>
16
15
<date>&TIMESTAMP;</date>
19
18
<firstname>Björn</firstname>
20
19
<surname>Påhlsson</surname>
22
<email>belorn@recompile.se</email>
21
<email>belorn@fukt.bsnet.se</email>
26
25
<firstname>Teddy</firstname>
27
26
<surname>Hogeborn</surname>
29
<email>teddy@recompile.se</email>
28
<email>teddy@fukt.bsnet.se</email>
44
34
<holder>Teddy Hogeborn</holder>
45
35
<holder>Björn Påhlsson</holder>
47
37
<xi:include href="legalnotice.xml"/>
51
41
<refentrytitle>&COMMANDNAME;</refentrytitle>
52
42
<manvolnum>8mandos</manvolnum>
56
46
<refname><command>&COMMANDNAME;</command></refname>
58
Run Mandos plugins, pass data from first to succeed.
48
Run Mandos plugins. Pass data from first succesful one.
64
54
<command>&COMMANDNAME;</command>
65
55
<group rep="repeat">
66
56
<arg choice="plain"><option>--global-env=<replaceable
67
>ENV</replaceable><literal>=</literal><replaceable
57
>VAR</replaceable><literal>=</literal><replaceable
68
58
>value</replaceable></option></arg>
69
<arg choice="plain"><option>-G
70
<replaceable>ENV</replaceable><literal>=</literal><replaceable
59
<arg choice="plain"><option>-e
60
<replaceable>VAR</replaceable><literal>=</literal><replaceable
71
61
>value</replaceable> </option></arg>
153
130
<title>DESCRIPTION</title>
155
132
<command>&COMMANDNAME;</command> is a program which is meant to
156
be specified as a <quote>keyscript</quote> for the root disk in
157
<citerefentry><refentrytitle>crypttab</refentrytitle>
158
<manvolnum>5</manvolnum></citerefentry>. The aim of this
159
program is therefore to output a password, which then
160
<citerefentry><refentrytitle>cryptsetup</refentrytitle>
161
<manvolnum>8</manvolnum></citerefentry> will use to unlock the
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.
165
142
This program is not meant to be invoked directly, but can be in
254
231
<option>--bar</option> with the option argument
255
232
<quote>baz</quote> is either
256
233
<userinput>--options-for=foo:--bar=baz</userinput> or
257
<userinput>--options-for=foo:--bar,baz</userinput>. Using
258
<userinput>--options-for="foo:--bar baz"</userinput>. will
259
<emphasis>not</emphasis> work.
234
<userinput>--options-for=foo:--bar,baz</userinput>, but
235
<emphasis>not</emphasis>
236
<userinput>--options-for="foo:--bar baz"</userinput>.
265
<term><option>--disable
242
<term><option> --disable
266
243
<replaceable>PLUGIN</replaceable></option></term>
268
245
<replaceable>PLUGIN</replaceable></option></term>
333
<term><option>--plugin-helper-dir
334
<replaceable>DIRECTORY</replaceable></option></term>
337
Specify a different plugin helper directory. The default
338
is <filename>/lib/mandos/plugin-helpers</filename>, which
339
will exist in the initial <acronym>RAM</acronym> disk
340
environment. (This will simply be passed to all plugins
341
via the <envar>MANDOSPLUGINHELPERDIR</envar> environment
342
variable. See <xref linkend="writing_plugins"/>)
348
<term><option>--config-file
349
<replaceable>FILE</replaceable></option></term>
352
Specify a different file to read additional options from.
353
See <xref linkend="files"/>. Other command line options
354
will override options specified in the file.
360
295
<term><option>--debug</option></term>
431
366
code will make this plugin-runner output the password from that
432
367
plugin, stop any other plugins, and exit.
435
<refsect2 id="writing_plugins">
436
<title>WRITING PLUGINS</title>
438
A plugin is simply a program which prints a password to its
439
standard output and then exits with a successful (zero) exit
440
status. If the exit status is not zero, any output on
441
standard output will be ignored by the plugin runner. Any
442
output on its standard error channel will simply be passed to
443
the standard error of the plugin runner, usually the system
447
If the password is a single-line, manually entered passprase,
448
a final trailing newline character should
449
<emphasis>not</emphasis> be printed.
452
The plugin will run in the initial RAM disk environment, so
453
care must be taken not to depend on any files or running
454
services not available there. Any helper executables required
455
by the plugin (which are not in the <envar>PATH</envar>) can
456
be placed in the plugin helper directory, the name of which
457
will be made available to the plugin via the
458
<envar>MANDOSPLUGINHELPERDIR</envar> environment variable.
461
The plugin must exit cleanly and free all allocated resources
462
upon getting the TERM signal, since this is what the plugin
463
runner uses to stop all other plugins when one plugin has
464
output a password and exited cleanly.
467
The plugin must not use resources, like for instance reading
468
from the standard input, without knowing that no other plugin
472
It is useful, but not required, for the plugin to take the
473
<option>--debug</option> option.
478
371
<refsect1 id="fallback">
528
415
of a line is ignored.
531
This program is meant to run in the initial RAM disk
532
environment, so that is where this file is assumed to
533
exist. The file does not need to exist in the normal
537
418
This file will be processed <emphasis>before</emphasis>
538
419
the normal command line options, so the latter can
539
420
override the former, if need be.
542
This file name is the default; the file to read for
543
arguments can be changed using the
544
<option>--config-file</option> option.
549
<term><filename class="directory"
550
>/lib/mandos/plugins.d</filename></term>
553
The default plugin directory; can be changed by the
554
<option>--plugin-dir</option> option.
559
<term><filename class="directory"
560
>/lib/mandos/plugin-helpers</filename></term>
563
The default plugin helper directory; can be changed by
564
the <option>--plugin-helper-dir</option> option.
572
428
<refsect1 id="bugs">
573
429
<title>BUGS</title>
575
The <option>--config-file</option> option is ignored when
576
specified from within a configuration file.
431
There is no <option>--enable</option> option to enable disabled
578
<xi:include href="bugs.xml"/>
581
436
<refsect1 id="examples">
582
437
<title>EXAMPLE</title>
585
Normal invocation needs no options:
588
<userinput>&COMMANDNAME;</userinput>
593
Run the program, but not the plugins, in debug mode:
597
<!-- do not wrap this line -->
598
<userinput>&COMMANDNAME; --debug</userinput>
604
Run all plugins, but run the <quote>foo</quote> plugin in
609
<!-- do not wrap this line -->
610
<userinput>&COMMANDNAME; --options-for=foo:--debug</userinput>
616
Run all plugins, but not the program, in debug mode:
620
<!-- do not wrap this line -->
621
<userinput>&COMMANDNAME; --global-options=--debug</userinput>
627
Read a different configuration file, run plugins from a
628
different directory, specify an alternate plugin helper
629
directory and add two options to the
630
<citerefentry><refentrytitle >mandos-client</refentrytitle>
631
<manvolnum>8mandos</manvolnum></citerefentry> plugin:
635
<!-- do not wrap this line -->
636
<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>
641
442
<refsect1 id="security">
642
443
<title>SECURITY</title>
644
This program will, when starting, try to switch to another user.
645
If it is started as root, it will succeed, and will by default
646
switch to user and group 65534, which are assumed to be
647
non-privileged. This user and group is then what all plugins
648
will be started as. Therefore, the only way to run a plugin as
649
a privileged user is to have the set-user-ID or set-group-ID bit
650
set on the plugin executable file (see <citerefentry>
651
<refentrytitle>execve</refentrytitle><manvolnum>2</manvolnum>
655
If this program is used as a keyscript in <citerefentry
656
><refentrytitle>crypttab</refentrytitle><manvolnum>5</manvolnum>
657
</citerefentry>, there is a slight risk that if this program
658
fails to work, there might be no way to boot the system except
659
for booting from another media and editing the initial RAM disk
660
image to not run this program. This is, however, unlikely,
661
since the <citerefentry><refentrytitle
662
>password-prompt</refentrytitle><manvolnum>8mandos</manvolnum>
663
</citerefentry> plugin will read a password from the console in
664
case of failure of the other plugins, and this plugin runner
665
will also, in case of catastrophic failure, itself fall back to
666
asking and outputting a password on the console (see <xref
667
linkend="fallback"/>).
671
448
<refsect1 id="see_also">
672
449
<title>SEE ALSO</title>
674
<citerefentry><refentrytitle>intro</refentrytitle>
675
<manvolnum>8mandos</manvolnum></citerefentry>,
676
451
<citerefentry><refentrytitle>cryptsetup</refentrytitle>
677
452
<manvolnum>8</manvolnum></citerefentry>,
678
<citerefentry><refentrytitle>crypttab</refentrytitle>
679
<manvolnum>5</manvolnum></citerefentry>,
680
<citerefentry><refentrytitle>execve</refentrytitle>
681
<manvolnum>2</manvolnum></citerefentry>,
682
453
<citerefentry><refentrytitle>mandos</refentrytitle>
683
454
<manvolnum>8</manvolnum></citerefentry>,
684
455
<citerefentry><refentrytitle>password-prompt</refentrytitle>
685
456
<manvolnum>8mandos</manvolnum></citerefentry>,
686
<citerefentry><refentrytitle>mandos-client</refentrytitle>
457
<citerefentry><refentrytitle>password-request</refentrytitle>
687
458
<manvolnum>8mandos</manvolnum></citerefentry>