1
<?xml version="1.0" encoding="UTF-8"?>
2
<!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
3
"http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
4
<!ENTITY COMMANDNAME "splashy">
5
<!ENTITY TIMESTAMP "2017-02-23">
6
<!ENTITY % common SYSTEM "../common.ent">
10
<refentry xmlns:xi="http://www.w3.org/2001/XInclude">
12
<title>Mandos Manual</title>
13
<!-- NWalsh’s docbook scripts use this to generate the footer: -->
14
<productname>Mandos</productname>
15
<productnumber>&version;</productnumber>
16
<date>&TIMESTAMP;</date>
19
<firstname>Björn</firstname>
20
<surname>Påhlsson</surname>
22
<email>belorn@recompile.se</email>
26
<firstname>Teddy</firstname>
27
<surname>Hogeborn</surname>
29
<email>teddy@recompile.se</email>
44
<holder>Teddy Hogeborn</holder>
45
<holder>Björn Påhlsson</holder>
47
<xi:include href="../legalnotice.xml"/>
51
<refentrytitle>&COMMANDNAME;</refentrytitle>
52
<manvolnum>8mandos</manvolnum>
56
<refname><command>&COMMANDNAME;</command></refname>
57
<refpurpose>Mandos plugin to use splashy to get a
58
password.</refpurpose>
63
<command>&COMMANDNAME;</command>
67
<refsect1 id="description">
68
<title>DESCRIPTION</title>
70
This program prompts for a password using <citerefentry>
71
<refentrytitle>splashy_update</refentrytitle>
72
<manvolnum>8</manvolnum></citerefentry> and outputs any given
73
password to standard output. If no <citerefentry><refentrytitle
74
>splashy</refentrytitle><manvolnum>8</manvolnum></citerefentry>
75
process can be found, this program will immediately exit with an
76
exit code indicating failure.
79
This program is not very useful on its own. This program is
80
really meant to run as a plugin in the <application
81
>Mandos</application> client-side system, where it is used as a
82
fallback and alternative to retrieving passwords from a
83
<application >Mandos</application> server.
86
If this program is killed (presumably by
87
<citerefentry><refentrytitle>plugin-runner</refentrytitle>
88
<manvolnum>8mandos</manvolnum></citerefentry> because some other
89
plugin provided the password), it cannot tell <citerefentry>
90
<refentrytitle>splashy</refentrytitle><manvolnum>8</manvolnum>
91
</citerefentry> to abort requesting a password, because
92
<citerefentry><refentrytitle>splashy</refentrytitle>
93
<manvolnum>8</manvolnum></citerefentry> does not support this.
94
Therefore, this program will then <emphasis>kill</emphasis> the
95
running <citerefentry><refentrytitle>splashy</refentrytitle>
96
<manvolnum>8</manvolnum></citerefentry> process and start a
97
<emphasis>new</emphasis> one, using <quote><literal
98
>boot</literal></quote> as the only argument.
102
<refsect1 id="options">
103
<title>OPTIONS</title>
105
This program takes no options.
109
<refsect1 id="exit_status">
110
<title>EXIT STATUS</title>
112
If exit status is 0, the output from the program is the password
113
as it was read. Otherwise, if exit status is other than 0, the
114
program was interrupted or encountered an error, and any output
115
so far could be corrupt and/or truncated, and should therefore
120
<refsect1 id="environment">
121
<title>ENVIRONMENT</title>
124
<term><envar>cryptsource</envar></term>
125
<term><envar>crypttarget</envar></term>
128
If set, these environment variables will be assumed to
129
contain the source device name and the target device
130
mapper name, respectively, and will be shown as part of
134
These variables will normally be inherited from
135
<citerefentry><refentrytitle>plugin-runner</refentrytitle>
136
<manvolnum>8mandos</manvolnum></citerefentry>, which will
137
normally have inherited them from
138
<filename>/scripts/local-top/cryptroot</filename> in the
139
initial <acronym>RAM</acronym> disk environment, which will
140
have set them from parsing kernel arguments and
141
<filename>/conf/conf.d/cryptroot</filename> (also in the
142
initial RAM disk environment), which in turn will have been
143
created when the initial RAM disk image was created by
145
>/usr/share/initramfs-tools/hooks/cryptroot</filename>, by
146
extracting the information of the root file system from
147
<filename >/etc/crypttab</filename>.
150
This behavior is meant to exactly mirror the behavior of
151
<command>askpass</command>, the default password prompter.
158
<refsect1 id="files">
162
<term><filename>/sbin/splashy_update</filename></term>
165
This is the command run to retrieve a password from
166
<citerefentry><refentrytitle>splashy</refentrytitle>
167
<manvolnum>8</manvolnum></citerefentry>. See
168
<citerefentry><refentrytitle
169
>splashy_update</refentrytitle><manvolnum>8</manvolnum>
175
<term><filename>/proc</filename></term>
178
To find the running <citerefentry><refentrytitle
179
>splashy</refentrytitle><manvolnum>8</manvolnum>
180
</citerefentry>, this directory will be searched for
181
numeric entries which will be assumed to be directories.
182
In all those directories, the <filename>exe</filename>
183
entry will be used to determine the name of the running
184
binary and the effective user and group
185
<abbrev>ID</abbrev> of the process. See <citerefentry>
186
<refentrytitle>proc</refentrytitle><manvolnum
187
>5</manvolnum></citerefentry>.
192
<term><filename>/sbin/splashy</filename></term>
195
This is the name of the binary which will be searched for
196
in the process list. See <citerefentry><refentrytitle
197
>splashy</refentrytitle><manvolnum>8</manvolnum>
208
Killing <citerefentry><refentrytitle>splashy</refentrytitle>
209
<manvolnum>8</manvolnum></citerefentry> and starting a new one
210
is ugly, but necessary as long as it does not support aborting a
213
<xi:include href="../bugs.xml"/>
216
<refsect1 id="example">
217
<title>EXAMPLE</title>
219
Note that normally, this program will not be invoked directly,
220
but instead started by the Mandos <citerefentry><refentrytitle
221
>plugin-runner</refentrytitle><manvolnum>8mandos</manvolnum>
226
This program takes no options.
229
<userinput>&COMMANDNAME;</userinput>
234
<refsect1 id="security">
235
<title>SECURITY</title>
237
If this program is killed by a signal, it will kill the process
238
<abbrev>ID</abbrev> which at the start of this program was
239
determined to run <citerefentry><refentrytitle
240
>splashy</refentrytitle><manvolnum>8</manvolnum></citerefentry>
241
as root (see also <xref linkend="files"/>). There is a very
242
slight risk that, in the time between those events, that process
243
<abbrev>ID</abbrev> was freed and then taken up by another
244
process; the wrong process would then be killed. Now, this
245
program can only be killed by the user who started it; see
246
<citerefentry><refentrytitle>plugin-runner</refentrytitle>
247
<manvolnum>8mandos</manvolnum></citerefentry>. This program
248
should therefore be started by a completely separate
249
non-privileged user, and no other programs should be allowed to
250
run as that special user. This means that it is not recommended
251
to use the user "nobody" to start this program, as other
252
possibly less trusted programs could be running as "nobody", and
253
they would then be able to kill this program, triggering the
254
killing of the process <abbrev>ID</abbrev> which may or may not
255
be <citerefentry><refentrytitle>splashy</refentrytitle>
256
<manvolnum>8</manvolnum></citerefentry>.
259
The only other thing that could be considered worthy of note is
260
this: This program is meant to be run by <citerefentry>
261
<refentrytitle>plugin-runner</refentrytitle><manvolnum
262
>8mandos</manvolnum></citerefentry>, and will, when run
263
standalone, outside, in a normal environment, immediately output
264
on its standard output any presumably secret password it just
265
received. Therefore, when running this program standalone
266
(which should never normally be done), take care not to type in
267
any real secret password by force of habit, since it would then
268
immediately be shown as output.
272
<refsect1 id="see_also">
273
<title>SEE ALSO</title>
275
<citerefentry><refentrytitle>intro</refentrytitle>
276
<manvolnum>8mandos</manvolnum></citerefentry>,
277
<citerefentry><refentrytitle>crypttab</refentrytitle>
278
<manvolnum>5</manvolnum></citerefentry>,
279
<citerefentry><refentrytitle>plugin-runner</refentrytitle>
280
<manvolnum>8mandos</manvolnum></citerefentry>,
281
<citerefentry><refentrytitle>proc</refentrytitle>
282
<manvolnum>5</manvolnum></citerefentry>,
283
<citerefentry><refentrytitle>splashy</refentrytitle>
284
<manvolnum>8</manvolnum></citerefentry>,
285
<citerefentry><refentrytitle>splashy_update</refentrytitle>
286
<manvolnum>8</manvolnum></citerefentry>
290
<!-- Local Variables: -->
291
<!-- time-stamp-start: "<!ENTITY TIMESTAMP [\"']" -->
292
<!-- time-stamp-end: "[\"']>" -->
293
<!-- time-stamp-format: "%:y-%02m-%02d" -->
added
removed
plugins.d/splashy.xml
