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>
42
34
<holder>Teddy Hogeborn</holder>
43
35
<holder>Björn Påhlsson</holder>
45
37
<xi:include href="legalnotice.xml"/>
49
41
<refentrytitle>&COMMANDNAME;</refentrytitle>
50
42
<manvolnum>8mandos</manvolnum>
54
46
<refname><command>&COMMANDNAME;</command></refname>
56
Run Mandos plugins, pass data from first to succeed.
48
Run Mandos plugins. Pass data from first succesful one.
62
54
<command>&COMMANDNAME;</command>
63
55
<group rep="repeat">
64
56
<arg choice="plain"><option>--global-env=<replaceable
65
>ENV</replaceable><literal>=</literal><replaceable
57
>VAR</replaceable><literal>=</literal><replaceable
66
58
>value</replaceable></option></arg>
67
<arg choice="plain"><option>-G
68
<replaceable>ENV</replaceable><literal>=</literal><replaceable
59
<arg choice="plain"><option>-e
60
<replaceable>VAR</replaceable><literal>=</literal><replaceable
69
61
>value</replaceable> </option></arg>
151
130
<title>DESCRIPTION</title>
153
132
<command>&COMMANDNAME;</command> is a program which is meant to
154
be specified as a <quote>keyscript</quote> for the root disk in
155
<citerefentry><refentrytitle>crypttab</refentrytitle>
156
<manvolnum>5</manvolnum></citerefentry>. The aim of this
157
program is therefore to output a password, which then
158
<citerefentry><refentrytitle>cryptsetup</refentrytitle>
159
<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.
163
142
This program is not meant to be invoked directly, but can be in
252
231
<option>--bar</option> with the option argument
253
232
<quote>baz</quote> is either
254
233
<userinput>--options-for=foo:--bar=baz</userinput> or
255
<userinput>--options-for=foo:--bar,baz</userinput>. Using
256
<userinput>--options-for="foo:--bar baz"</userinput>. will
257
<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>.
263
<term><option>--disable
242
<term><option> --disable
264
243
<replaceable>PLUGIN</replaceable></option></term>
266
245
<replaceable>PLUGIN</replaceable></option></term>
331
<term><option>--plugin-helper-dir
332
<replaceable>DIRECTORY</replaceable></option></term>
335
Specify a different plugin helper directory. The default
336
is <filename>/lib/mandos/plugin-helpers</filename>, which
337
will exist in the initial <acronym>RAM</acronym> disk
338
environment. (This will simply be passed to all plugins
339
via the <envar>MANDOSPLUGINHELPERDIR</envar> environment
340
variable. See <xref linkend="writing_plugins"/>)
346
<term><option>--config-file
347
<replaceable>FILE</replaceable></option></term>
350
Specify a different file to read additional options from.
351
See <xref linkend="files"/>. Other command line options
352
will override options specified in the file.
358
295
<term><option>--debug</option></term>
429
366
code will make this plugin-runner output the password from that
430
367
plugin, stop any other plugins, and exit.
433
<refsect2 id="writing_plugins">
434
<title>WRITING PLUGINS</title>
436
A plugin is simply a program which prints a password to its
437
standard output and then exits with a successful (zero) exit
438
status. If the exit status is not zero, any output on
439
standard output will be ignored by the plugin runner. Any
440
output on its standard error channel will simply be passed to
441
the standard error of the plugin runner, usually the system
445
If the password is a single-line, manually entered passprase,
446
a final trailing newline character should
447
<emphasis>not</emphasis> be printed.
450
The plugin will run in the initial RAM disk environment, so
451
care must be taken not to depend on any files or running
452
services not available there. Any helper executables required
453
by the plugin (which are not in the <envar>PATH</envar>) can
454
be placed in the plugin helper directory, the name of which
455
will be made available to the plugin via the
456
<envar>MANDOSPLUGINHELPERDIR</envar> environment variable.
459
The plugin must exit cleanly and free all allocated resources
460
upon getting the TERM signal, since this is what the plugin
461
runner uses to stop all other plugins when one plugin has
462
output a password and exited cleanly.
465
The plugin must not use resources, like for instance reading
466
from the standard input, without knowing that no other plugin
470
It is useful, but not required, for the plugin to take the
471
<option>--debug</option> option.
476
371
<refsect1 id="fallback">
550
428
<refsect1 id="bugs">
551
429
<title>BUGS</title>
553
The <option>--config-file</option> option is ignored when
554
specified from within a configuration file.
431
There is no <option>--enable</option> option to enable disabled
558
436
<refsect1 id="examples">
559
437
<title>EXAMPLE</title>
562
Normal invocation needs no options:
565
<userinput>&COMMANDNAME;</userinput>
570
Run the program, but not the plugins, in debug mode:
574
<!-- do not wrap this line -->
575
<userinput>&COMMANDNAME; --debug</userinput>
581
Run all plugins, but run the <quote>foo</quote> plugin in
586
<!-- do not wrap this line -->
587
<userinput>&COMMANDNAME; --options-for=foo:--debug</userinput>
593
Run all plugins, but not the program, in debug mode:
597
<!-- do not wrap this line -->
598
<userinput>&COMMANDNAME; --global-options=--debug</userinput>
604
Read a different configuration file, run plugins from a
605
different directory, specify an alternate plugin helper
606
directory and add two options to the
607
<citerefentry><refentrytitle >mandos-client</refentrytitle>
608
<manvolnum>8mandos</manvolnum></citerefentry> plugin:
612
<!-- do not wrap this line -->
613
<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>
618
442
<refsect1 id="security">
619
443
<title>SECURITY</title>
621
This program will, when starting, try to switch to another user.
622
If it is started as root, it will succeed, and will by default
623
switch to user and group 65534, which are assumed to be
624
non-privileged. This user and group is then what all plugins
625
will be started as. Therefore, the only way to run a plugin as
626
a privileged user is to have the set-user-ID or set-group-ID bit
627
set on the plugin executable file (see <citerefentry>
628
<refentrytitle>execve</refentrytitle><manvolnum>2</manvolnum>
632
If this program is used as a keyscript in <citerefentry
633
><refentrytitle>crypttab</refentrytitle><manvolnum>5</manvolnum>
634
</citerefentry>, there is a slight risk that if this program
635
fails to work, there might be no way to boot the system except
636
for booting from another media and editing the initial RAM disk
637
image to not run this program. This is, however, unlikely,
638
since the <citerefentry><refentrytitle
639
>password-prompt</refentrytitle><manvolnum>8mandos</manvolnum>
640
</citerefentry> plugin will read a password from the console in
641
case of failure of the other plugins, and this plugin runner
642
will also, in case of catastrophic failure, itself fall back to
643
asking and outputting a password on the console (see <xref
644
linkend="fallback"/>).
648
448
<refsect1 id="see_also">
649
449
<title>SEE ALSO</title>
651
<citerefentry><refentrytitle>intro</refentrytitle>
652
<manvolnum>8mandos</manvolnum></citerefentry>,
653
451
<citerefentry><refentrytitle>cryptsetup</refentrytitle>
654
452
<manvolnum>8</manvolnum></citerefentry>,
655
<citerefentry><refentrytitle>crypttab</refentrytitle>
656
<manvolnum>5</manvolnum></citerefentry>,
657
<citerefentry><refentrytitle>execve</refentrytitle>
658
<manvolnum>2</manvolnum></citerefentry>,
659
453
<citerefentry><refentrytitle>mandos</refentrytitle>
660
454
<manvolnum>8</manvolnum></citerefentry>,
661
455
<citerefentry><refentrytitle>password-prompt</refentrytitle>
662
456
<manvolnum>8mandos</manvolnum></citerefentry>,
663
<citerefentry><refentrytitle>mandos-client</refentrytitle>
457
<citerefentry><refentrytitle>password-request</refentrytitle>
664
458
<manvolnum>8mandos</manvolnum></citerefentry>