127
127
</refsynopsisdiv>
129
129
<refsect1 id="description">
130
130
<title>DESCRIPTION</title>
132
<command>&COMMANDNAME;</command> is a plugin runner that waits
133
for any of its plugins to return sucessfull with a password, and
134
passes it to cryptsetup as stdout message. This command is not
135
meant to be invoked directly, but is instead meant to be run by
136
cryptsetup by being specified in /etc/crypttab as a keyscript
137
and subsequlently started in the initrd environment. See
138
<citerefentry><refentrytitle>crypttab</refentrytitle>
139
<manvolnum>5</manvolnum></citerefentry> for more information on
144
plugins is looked for in the plugins directory which by default will be
145
/conf/conf.d/mandos/plugins.d if not changed by option --plugin-dir.
132
<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.
142
This program is not meant to be invoked directly, but can be in
143
order to test it. Note that any password obtained will simply
144
be output on standard output.
148
<refsect1 id="purpose">
149
<title>PURPOSE</title>
151
The purpose of this is to enable <emphasis>remote and unattended
152
rebooting</emphasis> of client host computer with an
153
<emphasis>encrypted root file system</emphasis>. See <xref
154
linkend="overview"/> for details.
149
159
<title>OPTIONS</title>
162
<term><option>--global-env
163
<replaceable>VAR</replaceable><literal>=</literal><replaceable
164
>value</replaceable></option></term>
166
<replaceable>VAR</replaceable><literal>=</literal><replaceable
167
>value</replaceable></option></term>
176
<term><option>--env-for
177
<replaceable>PLUGIN</replaceable><literal>:</literal
178
><replaceable>ENV</replaceable><literal>=</literal
179
><replaceable>value</replaceable></option></term>
181
<replaceable>PLUGIN</replaceable><literal>:</literal
182
><replaceable>ENV</replaceable><literal>=</literal
183
><replaceable>value</replaceable></option></term>
152
191
<term><option>--global-options
153
192
<replaceable>OPTIONS</replaceable></option></term>
155
194
<replaceable>OPTIONS</replaceable></option></term>
158
Global options given to all plugins as additional start
159
arguments. Options are specified with a -o flag followed
160
by a comma separated string of options.
197
Pass some options to <emphasis>all</emphasis> plugins.
198
<replaceable>OPTIONS</replaceable> is a comma separated
199
list of options. This is not a very useful option, except
200
for specifying the <quote><option>--debug</option></quote>
166
207
<term><option>--options-for
167
208
<replaceable>PLUGIN</replaceable><literal>:</literal
171
212
><replaceable>OPTION</replaceable></option></term>
174
Plugin specific options given to the plugin as additional
175
start arguments. Options are specified with a -o flag
176
followed by a comma separated string of options.
215
Pass some options to a specific plugin. <replaceable
216
>PLUGIN</replaceable> is the name (file basename) of a
217
plugin, and <replaceable>OPTIONS</replaceable> is a comma
218
separated list of options.
221
Note that since options are not split on whitespace, the
222
way to pass, to the plugin
223
<quote><filename>foo</filename></quote>, the option
224
<option>--bar</option> with the option argument
225
<quote>baz</quote> is either
226
<userinput>--options-for=foo:--bar=baz</userinput> or
227
<userinput>--options-for=foo:--bar,baz</userinput>, but
228
<emphasis>not</emphasis>
229
<userinput>--options-for="foo:--bar baz"</userinput>.
224
288
<term><option>--debug</option></term>
291
Enable debug mode. This will enable a lot of output to
292
standard error about what the program is doing. The
293
program will still perform all other functions normally.
294
The default is to <emphasis>not</emphasis> run in debug
298
The plugins will <emphasis>not</emphasis> be affected by
300
<userinput><option>--global-options=--debug</option></userinput>
301
if complete debugging eruption is desired.
253
327
<term><option>-V</option></term>
256
Prints the program version
330
Prints the program version.
337
<refsect1 id="overview">
338
<title>OVERVIEW</title>
339
<xi:include href="overview.xml"/>
341
This program will run on the client side in the initial
342
<acronym>RAM</acronym> disk environment, and is responsible for
343
getting a password. It does this by running plugins, one of
344
which will normally be the actual client program communicating
348
<refsect1 id="plugins">
349
<title>PLUGINS</title>
351
This program will get a password by running a number of
352
<firstterm>plugins</firstterm>, which are simply executable
353
programs in a directory in the initial <acronym>RAM</acronym>
354
disk environment. The default directory is
355
<filename>/lib/mandos/plugins.d</filename>, but this can be
356
changed with the <option>--plugin-dir</option> option. The
357
plugins are started in parallel, and the first plugin to output
358
a password <emphasis>and</emphasis> exit with a successful exit
359
code will make this plugin-runner output the password from that
360
plugin, stop any other plugins, and exit.
364
<refsect1 id="fallback">
365
<title>FALLBACK</title>
367
If no plugins succeed, this program will, as a fallback, ask for
368
a password on the console using <citerefentry><refentrytitle
369
>getpass</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
370
and output it. This is not meant to be the normal mode of
371
operation, as there is a separate plugin for getting a password
263
376
<refsect1 id="exit_status">
264
377
<title>EXIT STATUS</title>
379
Exit status of this program is zero if no errors were
380
encountered, and otherwise not. The fallback (see <xref
381
linkend="fallback"/>) may or may not have succeeded in either
386
<refsect1 id="environment">
387
<title>ENVIRONMENT</title>
269
393
<refsect1 id="file">
270
394
<title>FILES</title>
275
<refsect1 id="notes">
399
>/conf/conf.d/mandos/plugin-runner.conf</filename></term>
402
Since this program will be run as a keyscript, there is
403
little to no opportunity to pass command line arguments
404
to it. Therefore, it will <emphasis>also</emphasis>
405
read this file and use its contents as
406
whitespace-separated command line options. Also,
407
everything from a <quote>#</quote> character to the end
408
of a line is ignored.