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

  • Committer: teddy at recompile
  • Date: 2020-02-05 21:39:28 UTC
  • mto: This revision was merged to the branch mainline in revision 396.
  • Revision ID: teddy@recompile.se-20200205213928-vpvt0fwfg47ikv6f
Allow users to alter ask-password-mandos.service

If a user uses dracut with systemd and wishes to modify the options
passed to password-agent(8mandos) or mandos-client(8mandos), they
should be able to do so by simply creating a file
/etc/systemd/system/ask-password-mandos.service.d/override.conf,
containing, for instance:

[Service]
Environment=MANDOS_CLIENT_OPTIONS=--debug

Adding PASSWORD_AGENT_OPTIONS should also be possible (but should not
normally be needed).

* dracut-module/ask-password-mandos.service ([Service]/ExecStart): Add
  $PASSWORD_AGENT_OPTIONS before "--" and "$MANDOS_CLIENT_OPTIONS" to
  end of line.
* dracut-module/module-setup.sh (install): Install all files named
  /etc/systemd/system/ask-password-mandos.service.d/*.conf if any
  exists.  Also add --dh-params before $MANDOS_CLIENT_OPTIONS instead
  of at end of line.

Show diffs side-by-side

added added

removed removed

Lines of Context:
plugins.d/splashy.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 "splashy">
5
 
<!ENTITY TIMESTAMP "2018-02-08">
 
5
<!ENTITY TIMESTAMP "2019-02-10">
6
6
<!ENTITY % common SYSTEM "../common.ent">
7
7
%common;
8
8
]>
42
42
      <year>2016</year>
43
43
      <year>2017</year>
44
44
      <year>2018</year>
 
45
      <year>2019</year>
45
46
      <holder>Teddy Hogeborn</holder>
46
47
      <holder>Björn Påhlsson</holder>
47
48
    </copyright>
134
135
        <para>
135
136
          These variables will normally be inherited from
136
137
          <citerefentry><refentrytitle>plugin-runner</refentrytitle>
137
 
          <manvolnum>8mandos</manvolnum></citerefentry>, which will
138
 
          normally have inherited them from
139
 
          <filename>/scripts/local-top/cryptroot</filename> in the
140
 
          initial <acronym>RAM</acronym> disk environment, which will
141
 
          have set them from parsing kernel arguments and
142
 
          <filename>/conf/conf.d/cryptroot</filename> (also in the
143
 
          initial RAM disk environment), which in turn will have been
144
 
          created when the initial RAM disk image was created by
145
 
          <filename
146
 
          >/usr/share/initramfs-tools/hooks/cryptroot</filename>, by
147
 
          extracting the information of the root file system from
148
 
          <filename >/etc/crypttab</filename>.
 
138
          <manvolnum>8mandos</manvolnum></citerefentry>, which might
 
139
          have in turn inherited them from its calling process.
149
140
        </para>
150
141
        <para>
151
142
          This behavior is meant to exactly mirror the behavior of
275
266
    <para>
276
267
      <citerefentry><refentrytitle>intro</refentrytitle>
277
268
      <manvolnum>8mandos</manvolnum></citerefentry>,
278
 
      <citerefentry><refentrytitle>crypttab</refentrytitle>
279
 
      <manvolnum>5</manvolnum></citerefentry>,
280
269
      <citerefentry><refentrytitle>plugin-runner</refentrytitle>
281
270
      <manvolnum>8mandos</manvolnum></citerefentry>,
282
271
      <citerefentry><refentrytitle>proc</refentrytitle>