/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 plugin-runner.xml

  • Committer: teddy at recompile
  • Date: 2020-01-18 00:57:30 UTC
  • mto: This revision was merged to the branch mainline in revision 396.
  • Revision ID: teddy@recompile.se-20200118005730-rysosg44wz5gyxf8
DBUS-API: Order properties alphabetically

In the documentation for the D-Bus API, list the client object
properties in alphabetical order.

Show diffs side-by-side

added added

removed removed

Lines of Context:
1
1
<?xml version="1.0" encoding="UTF-8"?>
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
 
<!ENTITY VERSION "1.0">
5
4
<!ENTITY COMMANDNAME "plugin-runner">
6
 
<!ENTITY TIMESTAMP "2008-09-02">
 
5
<!ENTITY TIMESTAMP "2019-07-26">
 
6
<!ENTITY % common SYSTEM "common.ent">
 
7
%common;
7
8
]>
8
9
 
9
10
<refentry xmlns:xi="http://www.w3.org/2001/XInclude">
11
12
    <title>Mandos Manual</title>
12
13
    <!-- Nwalsh’s docbook scripts use this to generate the footer: -->
13
14
    <productname>Mandos</productname>
14
 
    <productnumber>&VERSION;</productnumber>
 
15
    <productnumber>&version;</productnumber>
15
16
    <date>&TIMESTAMP;</date>
16
17
    <authorgroup>
17
18
      <author>
18
19
        <firstname>Björn</firstname>
19
20
        <surname>Påhlsson</surname>
20
21
        <address>
21
 
          <email>belorn@fukt.bsnet.se</email>
 
22
          <email>belorn@recompile.se</email>
22
23
        </address>
23
24
      </author>
24
25
      <author>
25
26
        <firstname>Teddy</firstname>
26
27
        <surname>Hogeborn</surname>
27
28
        <address>
28
 
          <email>teddy@fukt.bsnet.se</email>
 
29
          <email>teddy@recompile.se</email>
29
30
        </address>
30
31
      </author>
31
32
    </authorgroup>
32
33
    <copyright>
33
34
      <year>2008</year>
 
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>
34
46
      <holder>Teddy Hogeborn</holder>
35
47
      <holder>Björn Påhlsson</holder>
36
48
    </copyright>
37
49
    <xi:include href="legalnotice.xml"/>
38
50
  </refentryinfo>
39
 
 
 
51
  
40
52
  <refmeta>
41
53
    <refentrytitle>&COMMANDNAME;</refentrytitle>
42
54
    <manvolnum>8mandos</manvolnum>
45
57
  <refnamediv>
46
58
    <refname><command>&COMMANDNAME;</command></refname>
47
59
    <refpurpose>
48
 
      Run Mandos plugins.  Pass data from first succesful one.
 
60
      Run Mandos plugins, pass data from first to succeed.
49
61
    </refpurpose>
50
62
  </refnamediv>
51
 
 
 
63
  
52
64
  <refsynopsisdiv>
53
65
    <cmdsynopsis>
54
66
      <command>&COMMANDNAME;</command>
55
67
      <group rep="repeat">
56
68
        <arg choice="plain"><option>--global-env=<replaceable
57
 
        >VAR</replaceable><literal>=</literal><replaceable
 
69
        >ENV</replaceable><literal>=</literal><replaceable
58
70
        >value</replaceable></option></arg>
59
71
        <arg choice="plain"><option>-G
60
 
        <replaceable>VAR</replaceable><literal>=</literal><replaceable
 
72
        <replaceable>ENV</replaceable><literal>=</literal><replaceable
61
73
        >value</replaceable> </option></arg>
62
74
      </group>
63
75
      <sbr/>
111
123
      <arg><option>--plugin-dir=<replaceable
112
124
      >DIRECTORY</replaceable></option></arg>
113
125
      <sbr/>
 
126
      <arg><option>--plugin-helper-dir=<replaceable
 
127
      >DIRECTORY</replaceable></option></arg>
 
128
      <sbr/>
114
129
      <arg><option>--config-file=<replaceable
115
130
      >FILE</replaceable></option></arg>
116
131
      <sbr/>
140
155
    <title>DESCRIPTION</title>
141
156
    <para>
142
157
      <command>&COMMANDNAME;</command> is a program which is meant to
143
 
      be specified as <quote>keyscript</quote> in <citerefentry>
144
 
      <refentrytitle>crypttab</refentrytitle>
145
 
      <manvolnum>5</manvolnum></citerefentry> for the root disk.  The
146
 
      aim of this program is therefore to output a password, which
147
 
      then <citerefentry><refentrytitle>cryptsetup</refentrytitle>
 
158
      be specified as a <quote>keyscript</quote> for the root disk in
 
159
      <citerefentry><refentrytitle>crypttab</refentrytitle>
 
160
      <manvolnum>5</manvolnum></citerefentry>.  The aim of this
 
161
      program is therefore to output a password, which then
 
162
      <citerefentry><refentrytitle>cryptsetup</refentrytitle>
148
163
      <manvolnum>8</manvolnum></citerefentry> will use to unlock the
149
164
      root disk.
150
165
    </para>
170
185
    <variablelist>
171
186
      <varlistentry>
172
187
        <term><option>--global-env
173
 
        <replaceable>VAR</replaceable><literal>=</literal><replaceable
 
188
        <replaceable>ENV</replaceable><literal>=</literal><replaceable
174
189
        >value</replaceable></option></term>
175
190
        <term><option>-G
176
 
        <replaceable>VAR</replaceable><literal>=</literal><replaceable
 
191
        <replaceable>ENV</replaceable><literal>=</literal><replaceable
177
192
        >value</replaceable></option></term>
178
193
        <listitem>
179
194
          <para>
247
262
          </para>
248
263
        </listitem>
249
264
      </varlistentry>
250
 
 
 
265
      
251
266
      <varlistentry>
252
267
        <term><option>--disable
253
268
        <replaceable>PLUGIN</replaceable></option></term>
258
273
            Disable the plugin named
259
274
            <replaceable>PLUGIN</replaceable>.  The plugin will not be
260
275
            started.
261
 
          </para>       
 
276
          </para>
262
277
        </listitem>
263
278
      </varlistentry>
264
 
 
 
279
      
265
280
      <varlistentry>
266
281
        <term><option>--enable
267
282
        <replaceable>PLUGIN</replaceable></option></term>
272
287
            Re-enable the plugin named
273
288
            <replaceable>PLUGIN</replaceable>.  This is only useful to
274
289
            undo a previous <option>--disable</option> option, maybe
275
 
            from the config file.
 
290
            from the configuration file.
276
291
          </para>
277
292
        </listitem>
278
293
      </varlistentry>
279
 
 
 
294
      
280
295
      <varlistentry>
281
296
        <term><option>--groupid
282
297
        <replaceable>ID</replaceable></option></term>
289
304
          </para>
290
305
        </listitem>
291
306
      </varlistentry>
292
 
 
 
307
      
293
308
      <varlistentry>
294
309
        <term><option>--userid
295
310
        <replaceable>ID</replaceable></option></term>
302
317
          </para>
303
318
        </listitem>
304
319
      </varlistentry>
305
 
 
 
320
      
306
321
      <varlistentry>
307
322
        <term><option>--plugin-dir
308
323
        <replaceable>DIRECTORY</replaceable></option></term>
317
332
      </varlistentry>
318
333
      
319
334
      <varlistentry>
 
335
        <term><option>--plugin-helper-dir
 
336
        <replaceable>DIRECTORY</replaceable></option></term>
 
337
        <listitem>
 
338
          <para>
 
339
            Specify a different plugin helper directory.  The default
 
340
            is <filename>/lib/mandos/plugin-helpers</filename>, which
 
341
            will exist in the initial <acronym>RAM</acronym> disk
 
342
            environment.  (This will simply be passed to all plugins
 
343
            via the <envar>MANDOSPLUGINHELPERDIR</envar> environment
 
344
            variable.  See <xref linkend="writing_plugins"/>)
 
345
          </para>
 
346
        </listitem>
 
347
      </varlistentry>
 
348
      
 
349
      <varlistentry>
320
350
        <term><option>--config-file
321
351
        <replaceable>FILE</replaceable></option></term>
322
352
        <listitem>
365
395
          </para>
366
396
        </listitem>
367
397
      </varlistentry>
368
 
 
 
398
      
369
399
      <varlistentry>
370
400
        <term><option>--version</option></term>
371
401
        <term><option>-V</option></term>
377
407
      </varlistentry>
378
408
    </variablelist>
379
409
  </refsect1>
380
 
 
 
410
  
381
411
  <refsect1 id="overview">
382
412
    <title>OVERVIEW</title>
383
413
    <xi:include href="overview.xml"/>
403
433
      code will make this plugin-runner output the password from that
404
434
      plugin, stop any other plugins, and exit.
405
435
    </para>
406
 
 
 
436
    
407
437
    <refsect2 id="writing_plugins">
408
438
      <title>WRITING PLUGINS</title>
409
439
      <para>
416
446
        console.
417
447
      </para>
418
448
      <para>
 
449
        If the password is a single-line, manually entered passprase,
 
450
        a final trailing newline character should
 
451
        <emphasis>not</emphasis> be printed.
 
452
      </para>
 
453
      <para>
419
454
        The plugin will run in the initial RAM disk environment, so
420
455
        care must be taken not to depend on any files or running
421
 
        services not available there.
 
456
        services not available there.  Any helper executables required
 
457
        by the plugin (which are not in the <envar>PATH</envar>) can
 
458
        be placed in the plugin helper directory, the name of which
 
459
        will be made available to the plugin via the
 
460
        <envar>MANDOSPLUGINHELPERDIR</envar> environment variable.
422
461
      </para>
423
462
      <para>
424
463
        The plugin must exit cleanly and free all allocated resources
428
467
      </para>
429
468
      <para>
430
469
        The plugin must not use resources, like for instance reading
431
 
        from the standard input, without knowing that no other plugins
432
 
        are also using it.
 
470
        from the standard input, without knowing that no other plugin
 
471
        is also using it.
433
472
      </para>
434
473
      <para>
435
474
        It is useful, but not required, for the plugin to take the
467
506
      only passes on its environment to all the plugins.  The
468
507
      environment passed to plugins can be modified using the
469
508
      <option>--global-env</option> and <option>--env-for</option>
470
 
      optins.
 
509
      options.  Also, the <option>--plugin-helper-dir</option> option
 
510
      will affect the environment variable
 
511
      <envar>MANDOSPLUGINHELPERDIR</envar> for the plugins.
471
512
    </para>
472
513
  </refsect1>
473
514
  
506
547
            </para>
507
548
          </listitem>
508
549
        </varlistentry>
 
550
        <varlistentry>
 
551
          <term><filename class="directory"
 
552
          >/lib/mandos/plugins.d</filename></term>
 
553
          <listitem>
 
554
            <para>
 
555
              The default plugin directory; can be changed by the
 
556
              <option>--plugin-dir</option> option.
 
557
            </para>
 
558
          </listitem>
 
559
        </varlistentry>
 
560
        <varlistentry>
 
561
          <term><filename class="directory"
 
562
          >/lib/mandos/plugin-helpers</filename></term>
 
563
          <listitem>
 
564
            <para>
 
565
              The default plugin helper directory; can be changed by
 
566
              the <option>--plugin-helper-dir</option> option.
 
567
            </para>
 
568
          </listitem>
 
569
        </varlistentry>
509
570
      </variablelist>
510
571
    </para>
511
572
  </refsect1>
512
573
  
513
 
<!--   <refsect1 id="bugs"> -->
514
 
<!--     <title>BUGS</title> -->
515
 
<!--     <para> -->
516
 
<!--     </para> -->
517
 
<!--   </refsect1> -->
 
574
  <refsect1 id="bugs">
 
575
    <title>BUGS</title>
 
576
    <para>
 
577
      The <option>--config-file</option> option is ignored when
 
578
      specified from within a configuration file.
 
579
    </para>
 
580
    <xi:include href="bugs.xml"/>
 
581
  </refsect1>
518
582
  
519
583
  <refsect1 id="examples">
520
584
    <title>EXAMPLE</title>
562
626
    </informalexample>
563
627
    <informalexample>
564
628
      <para>
565
 
        Run plugins from a different directory and add a special
566
 
        option to the <citerefentry><refentrytitle
567
 
        >password-request</refentrytitle>
 
629
        Read a different configuration file, run plugins from a
 
630
        different directory, specify an alternate plugin helper
 
631
        directory and add four options to the
 
632
        <citerefentry><refentrytitle >mandos-client</refentrytitle>
568
633
        <manvolnum>8mandos</manvolnum></citerefentry> plugin:
569
634
      </para>
570
635
      <para>
571
636
 
572
637
<!-- do not wrap this line -->
573
 
<userinput>&COMMANDNAME;  --plugin-dir=plugins.d --options-for=password-request:--keydir=keydir</userinput>
 
638
<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,&#x200b;--seckey=seckey.txt,&#x200b;--tls-pubkey=tls-pubkey.pem,&#x200b;--tls-privkey=tls-privkey.pem</userinput>
574
639
 
575
640
      </para>
576
641
    </informalexample>
584
649
      non-privileged.  This user and group is then what all plugins
585
650
      will be started as.  Therefore, the only way to run a plugin as
586
651
      a privileged user is to have the set-user-ID or set-group-ID bit
587
 
      set on the plugin executable files (see <citerefentry>
 
652
      set on the plugin executable file (see <citerefentry>
588
653
      <refentrytitle>execve</refentrytitle><manvolnum>2</manvolnum>
589
654
      </citerefentry>).
590
655
    </para>
591
656
    <para>
592
657
      If this program is used as a keyscript in <citerefentry
593
658
      ><refentrytitle>crypttab</refentrytitle><manvolnum>5</manvolnum>
594
 
      </citerefentry>, there is a risk that if this program fails to
595
 
      work, there might be no way to boot the system except for
596
 
      booting from another media and editing the initial RAM disk
 
659
      </citerefentry>, there is a slight risk that if this program
 
660
      fails to work, there might be no way to boot the system except
 
661
      for booting from another media and editing the initial RAM disk
597
662
      image to not run this program.  This is, however, unlikely,
598
663
      since the <citerefentry><refentrytitle
599
664
      >password-prompt</refentrytitle><manvolnum>8mandos</manvolnum>
608
673
  <refsect1 id="see_also">
609
674
    <title>SEE ALSO</title>
610
675
    <para>
 
676
      <citerefentry><refentrytitle>intro</refentrytitle>
 
677
      <manvolnum>8mandos</manvolnum></citerefentry>,
611
678
      <citerefentry><refentrytitle>cryptsetup</refentrytitle>
612
679
      <manvolnum>8</manvolnum></citerefentry>,
613
680
      <citerefentry><refentrytitle>crypttab</refentrytitle>
618
685
      <manvolnum>8</manvolnum></citerefentry>,
619
686
      <citerefentry><refentrytitle>password-prompt</refentrytitle>
620
687
      <manvolnum>8mandos</manvolnum></citerefentry>,
621
 
      <citerefentry><refentrytitle>password-request</refentrytitle>
 
688
      <citerefentry><refentrytitle>mandos-client</refentrytitle>
622
689
      <manvolnum>8mandos</manvolnum></citerefentry>
623
690
    </para>
624
691
  </refsect1>