/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 Hogeborn
  • Date: 2019-03-04 20:39:48 UTC
  • mto: (237.7.594 trunk)
  • mto: This revision was merged to the branch mainline in revision 382.
  • Revision ID: teddy@recompile.se-20190304203948-x8cdobs47h1f89xk
mandos-ctl: Bug fix: fix client/properties confusion

* mandos-ctl (Command.run_on_one_client): Take an additional
                                          "properties" argument.  All
                                          callers and users changed.
  (IsEnabledCmd.is_enabled): Don't run client.Get(); just look at the
                             "Enabled" property key.
  (TestCmd.setUp): Set self.clients to the correct form of dict, and
                   set self.one_client to be a dict with only one
                   client.  Also set self.other_client to other client
                   object.  All users of these attributes changed.
  (TestCmd.setUp.MockClient.__getitem__): Removed.
  (TestCmd.setUp.MockClient.__setitem__): - '' -
  (TestIsEnabled.test_is_enabled_does_get_attribute): Removed.
  (TestIsEnabled.test_is_enabled_run_exits_with_failure): Don't use []
  to alter client attribute; modify client.attributes dict directly.
  (TestRemoveCmd.test_remove): Run on full client list.
  (TestApproveCmd.test_approve): - '' -
  (TestDenyCmd.test_approve): - '' - and rename to "test_deny".

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>