/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/usplash.xml

* network-hooks.d/bridge: Use "/usr/sbin/brctl" explicitly.
* plugins.d/mandos-client.c (run_network_hooks): Raise priviliges in
                                                 child process.
  (main): Do not use getuid() to check if running setuid root.  Do not
          raise privileges for run_network_hooks.

Show diffs side-by-side

added added

removed removed

Lines of Context:
plugins.d/usplash.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 "usplash">
5
 
<!ENTITY TIMESTAMP "2019-02-10">
 
5
<!ENTITY TIMESTAMP "2011-10-03">
6
6
<!ENTITY % common SYSTEM "../common.ent">
7
7
%common;
8
8
]>
33
33
    <copyright>
34
34
      <year>2008</year>
35
35
      <year>2009</year>
36
 
      <year>2010</year>
37
36
      <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>
46
37
      <holder>Teddy Hogeborn</holder>
47
38
      <holder>Björn Påhlsson</holder>
48
39
    </copyright>
135
126
        <para>
136
127
          These variables will normally be inherited from
137
128
          <citerefentry><refentrytitle>plugin-runner</refentrytitle>
138
 
          <manvolnum>8mandos</manvolnum></citerefentry>, which might
139
 
          have in turn inherited them from its calling process.
 
129
          <manvolnum>8mandos</manvolnum></citerefentry>, which will
 
130
          normally have inherited them from
 
131
          <filename>/scripts/local-top/cryptroot</filename> in the
 
132
          initial <acronym>RAM</acronym> disk environment, which will
 
133
          have set them from parsing kernel arguments and
 
134
          <filename>/conf/conf.d/cryptroot</filename> (also in the
 
135
          initial RAM disk environment), which in turn will have been
 
136
          created when the initial RAM disk image was created by
 
137
          <filename
 
138
          >/usr/share/initramfs-tools/hooks/cryptroot</filename>, by
 
139
          extracting the information of the root file system from
 
140
          <filename >/etc/crypttab</filename>.
140
141
        </para>
141
142
        <para>
142
143
          This behavior is meant to exactly mirror the behavior of
177
178
        </listitem>
178
179
      </varlistentry>
179
180
      <varlistentry>
180
 
        <term><filename class="directory">/proc</filename></term>
 
181
        <term><filename>/proc</filename></term>
181
182
        <listitem>
182
183
          <para>
183
184
            To find the running <citerefentry><refentrytitle
216
217
      is ugly, but necessary as long as it does not support aborting a
217
218
      password request.
218
219
    </para>
219
 
    <xi:include href="../bugs.xml"/>
220
220
  </refsect1>
221
221
  
222
222
  <refsect1 id="example">
280
280
    <para>
281
281
      <citerefentry><refentrytitle>intro</refentrytitle>
282
282
      <manvolnum>8mandos</manvolnum></citerefentry>,
 
283
      <citerefentry><refentrytitle>crypttab</refentrytitle>
 
284
      <manvolnum>5</manvolnum></citerefentry>,
283
285
      <citerefentry><refentrytitle>fifo</refentrytitle>
284
286
      <manvolnum>7</manvolnum></citerefentry>,
285
287
      <citerefentry><refentrytitle>plugin-runner</refentrytitle>