/mandos/trunk

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

« back to all changes in this revision

Viewing changes to plugins.d/splashy.xml

  • Committer: Teddy Hogeborn
  • Date: 2019-03-10 02:35:22 UTC
  • Revision ID: teddy@recompile.se-20190310023522-cvos2tw2si6t7if3
mandos-ctl: Minimize number of D-Bus calls

* mandos-ctl (Command.run): Now takes a {objpath: properties} dict,
                            followed by optional "bus" and "mandos"
                            arguments.  Use "bus" to connect to
                            clients when dispatching to method
                            run_on_one_client().  All callers changed.
  (IsEnabledCmd.run): New.
  (IsEnabledCmd.run_on_one_client): Remove.
  (ApproveCmd.run_on_one_client): Add busname to debug output.
  (DenyCmd.run_on_one_client): - '' -
  (main): In D-Bus debug output, change "name" to "busname".  Also,
          don't connect to clients, just use the object path as the
          key of the "clients" dict passed to Command.run().
  (TestCmd.clients): Changed to an {objpath: properties} dict.
  (TestCmd.one_client): - '' -
  (TestCmd.bus): New mock bus object having a get_object() method.

Show diffs side-by-side

added added

removed removed

Lines of Context:
plugins.d/splashy.xml
135
135
        <para>
136
136
          These variables will normally be inherited from
137
137
          <citerefentry><refentrytitle>plugin-runner</refentrytitle>
138
 
          <manvolnum>8mandos</manvolnum></citerefentry>, which might
139
 
          have in turn inherited them from its calling process.
 
138
          <manvolnum>8mandos</manvolnum></citerefentry>, which will
 
139
          normally have inherited them from
 
140
          <filename>/scripts/local-top/cryptroot</filename> in the
 
141
          initial <acronym>RAM</acronym> disk environment, which will
 
142
          have set them from parsing kernel arguments and
 
143
          <filename>/conf/conf.d/cryptroot</filename> (also in the
 
144
          initial RAM disk environment), which in turn will have been
 
145
          created when the initial RAM disk image was created by
 
146
          <filename
 
147
          >/usr/share/initramfs-tools/hooks/cryptroot</filename>, by
 
148
          extracting the information of the root file system from
 
149
          <filename >/etc/crypttab</filename>.
140
150
        </para>
141
151
        <para>
142
152
          This behavior is meant to exactly mirror the behavior of
266
276
    <para>
267
277
      <citerefentry><refentrytitle>intro</refentrytitle>
268
278
      <manvolnum>8mandos</manvolnum></citerefentry>,
 
279
      <citerefentry><refentrytitle>crypttab</refentrytitle>
 
280
      <manvolnum>5</manvolnum></citerefentry>,
269
281
      <citerefentry><refentrytitle>plugin-runner</refentrytitle>
270
282
      <manvolnum>8mandos</manvolnum></citerefentry>,
271
283
      <citerefentry><refentrytitle>proc</refentrytitle>