/mandos/release

To get this branch, use:
bzr branch http://bzr.recompile.se/loggerhead/mandos/release

« back to all changes in this revision

Viewing changes to plugins.d/password-prompt.xml

  • Committer: Teddy Hogeborn
  • Date: 2024-09-16 21:01:52 UTC
  • mto: This revision was merged to the branch mainline in revision 412.
  • Revision ID: teddy@recompile.se-20240916210152-0xbv4b15jyho9ydk
Override lintian experimental tag "executable-in-usr-lib"

Lintian reports executable files in /usr/lib, since binaries which are
executed internally are supposed to be stored in /usr/libexec.  But
the executables we store in /usr/lib are all files to be copied into
the initial RAM disk image, and are never executed from their storage
location in /usr/lib.  Except one; the Dracut module-setup.sh file.
But that file seems to be required to be executable; the
module-setup.sh file of every other Dracut module is also an
executable file.

* debian/mandos-client.lintian-overrides: Override experimental tag
  "executable-in-usr-lib" about files which are not actually executed
  from this location, and only exist to be copied to the initial RAM
  disk image.  Also the Dracut module-setup.sh file, which merely
  follows the pattern of all other Dracut module-setup.sh files from
  other Dracut modules.

Show diffs side-by-side

added added

removed removed

Lines of Context:
plugins.d/password-prompt.xml
2
2
<!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
3
3
        "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
4
4
<!ENTITY COMMANDNAME "password-prompt">
5
 
<!ENTITY TIMESTAMP "2009-01-04">
 
5
<!ENTITY TIMESTAMP "2019-07-27">
6
6
<!ENTITY % common SYSTEM "../common.ent">
7
7
%common;
8
8
]>
19
19
        <firstname>Björn</firstname>
20
20
        <surname>Påhlsson</surname>
21
21
        <address>
22
 
          <email>belorn@fukt.bsnet.se</email>
 
22
          <email>belorn@recompile.se</email>
23
23
        </address>
24
24
      </author>
25
25
      <author>
26
26
        <firstname>Teddy</firstname>
27
27
        <surname>Hogeborn</surname>
28
28
        <address>
29
 
          <email>teddy@fukt.bsnet.se</email>
 
29
          <email>teddy@recompile.se</email>
30
30
        </address>
31
31
      </author>
32
32
    </authorgroup>
33
33
    <copyright>
34
34
      <year>2008</year>
35
35
      <year>2009</year>
 
36
      <year>2010</year>
 
37
      <year>2011</year>
 
38
      <year>2012</year>
 
39
      <year>2013</year>
 
40
      <year>2014</year>
 
41
      <year>2015</year>
 
42
      <year>2016</year>
 
43
      <year>2017</year>
 
44
      <year>2018</year>
 
45
      <year>2019</year>
36
46
      <holder>Teddy Hogeborn</holder>
37
47
      <holder>Björn Påhlsson</holder>
38
48
    </copyright>
59
69
        >PREFIX</replaceable></arg>
60
70
      </group>
61
71
      <sbr/>
 
72
      <arg choice="opt">
 
73
        <option>--prompt <replaceable>PROMPT</replaceable></option>
 
74
      </arg>
62
75
      <arg choice="opt"><option>--debug</option></arg>
63
76
    </cmdsynopsis>
64
77
    <cmdsynopsis>
100
113
      wrapper, although actual use of that function is not guaranteed
101
114
      or implied.
102
115
    </para>
 
116
    <para>
 
117
      This program tries to detect if a Plymouth daemon
 
118
      (<citerefentry><refentrytitle
 
119
      >plymouthd</refentrytitle><manvolnum>8</manvolnum></citerefentry>)
 
120
      is running, by looking for a
 
121
      <filename>/run/plymouth/pid</filename> file or a process named
 
122
      <quote><literal>plymouthd</literal></quote>.  If it is detected,
 
123
      this process will immediately exit without doing anything.
 
124
    </para>
103
125
  </refsect1>
104
126
  
105
127
  <refsect1 id="options">
128
150
      </varlistentry>
129
151
      
130
152
      <varlistentry>
 
153
        <term><option>--prompt=<replaceable
 
154
        >PROMPT</replaceable></option></term>
 
155
        <listitem>
 
156
          <para>
 
157
            The password prompt.  Using this option will make this
 
158
            program ignore the <envar>CRYPTTAB_SOURCE</envar> and
 
159
            <envar>CRYPTTAB_NAME</envar> environment variables.
 
160
          </para>
 
161
        </listitem>
 
162
      </varlistentry>
 
163
      
 
164
      <varlistentry>
131
165
        <term><option>--debug</option></term>
132
166
        <listitem>
133
167
          <para>
183
217
    <title>ENVIRONMENT</title>
184
218
    <variablelist>
185
219
      <varlistentry>
186
 
        <term><envar>cryptsource</envar></term>
187
 
        <term><envar>crypttarget</envar></term>
 
220
        <term><envar>CRYPTTAB_SOURCE</envar></term>
 
221
        <term><envar>CRYPTTAB_NAME</envar></term>
188
222
        <listitem>
189
223
          <para>
190
 
            If set, these environment variables will be assumed to
 
224
            If set, and if the <option>--prompt</option> option is not
 
225
            used, these environment variables will be assumed to
191
226
            contain the source device name and the target device
192
227
            mapper name, respectively, and will be shown as part of
193
228
            the prompt.
195
230
        <para>
196
231
          These variables will normally be inherited from
197
232
          <citerefentry><refentrytitle>plugin-runner</refentrytitle>
198
 
          <manvolnum>8mandos</manvolnum></citerefentry>, which will
199
 
          normally have inherited them from
200
 
          <filename>/scripts/local-top/cryptroot</filename> in the
201
 
          initial <acronym>RAM</acronym> disk environment, which will
202
 
          have set them from parsing kernel arguments and
203
 
          <filename>/conf/conf.d/cryptroot</filename> (also in the
204
 
          initial RAM disk environment), which in turn will have been
205
 
          created when the initial RAM disk image was created by
206
 
          <filename
207
 
          >/usr/share/initramfs-tools/hooks/cryptroot</filename>, by
208
 
          extracting the information of the root file system from
209
 
          <filename >/etc/crypttab</filename>.
 
233
          <manvolnum>8mandos</manvolnum></citerefentry>, which might
 
234
          have in turn inherited them from its calling process.
210
235
        </para>
211
236
        <para>
212
237
          This behavior is meant to exactly mirror the behavior of
213
 
          <command>askpass</command>, the default password prompter.
 
238
          <command>askpass</command>, the default password prompter
 
239
          from initramfs-tools.
214
240
        </para>
215
241
        </listitem>
216
242
      </varlistentry>
219
245
  
220
246
  <refsect1 id="bugs">
221
247
    <title>BUGS</title>
222
 
    <para>
223
 
      None are known at this time.
224
 
    </para>
 
248
    <xi:include href="../bugs.xml"/>
225
249
  </refsect1>
226
250
  
227
251
  <refsect1 id="example">
292
316
  <refsect1 id="see_also">
293
317
    <title>SEE ALSO</title>
294
318
    <para>
295
 
      <citerefentry><refentrytitle>crypttab</refentrytitle>
296
 
      <manvolnum>5</manvolnum></citerefentry>
 
319
      <citerefentry><refentrytitle>intro</refentrytitle>
 
320
      <manvolnum>8mandos</manvolnum></citerefentry>,
297
321
      <citerefentry><refentrytitle>mandos-client</refentrytitle>
298
 
      <manvolnum>8mandos</manvolnum></citerefentry>
 
322
      <manvolnum>8mandos</manvolnum></citerefentry>,
299
323
      <citerefentry><refentrytitle>plugin-runner</refentrytitle>
300
324
      <manvolnum>8mandos</manvolnum></citerefentry>,
 
325
      <citerefentry><refentrytitle>plymouthd</refentrytitle>
 
326
      <manvolnum>8</manvolnum></citerefentry>
301
327
    </para>
302
328
  </refsect1>
303
329
</refentry>