/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/password-prompt.xml

  • Committer: Teddy Hogeborn
  • Date: 2008-09-19 00:54:24 UTC
  • mto: This revision was merged to the branch mainline in revision 188.
  • Revision ID: teddy@fukt.bsnet.se-20080919005424-2kw5e1h9pjygj4ug
* debian/mandos.postinst: New. Create mandos user and group.

* debian/mandos.postrm: New.  Delete mandos user and group.

* initramfs-tools-hook: Add "--userid" and "--groupid" to
                        "plugin-runner.conf" if necessary.

Show diffs side-by-side

added added

removed removed

Lines of Context:
plugins.d/password-prompt.xml
3
3
        "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
4
4
<!ENTITY VERSION "1.0">
5
5
<!ENTITY COMMANDNAME "password-prompt">
6
 
<!ENTITY TIMESTAMP "2008-08-31">
 
6
<!ENTITY TIMESTAMP "2008-09-06">
7
7
]>
8
8
 
9
9
<refentry xmlns:xi="http://www.w3.org/2001/XInclude">
87
87
      is not very useful on its own.  This program is really meant to
88
88
      run as a plugin in the <application>Mandos</application>
89
89
      client-side system, where it is used as a fallback and
90
 
      alternative to retriving passwords from a <application
 
90
      alternative to retrieving passwords from a <application
91
91
      >Mandos</application> server.
92
92
    </para>
93
93
    <para>
194
194
          <manvolnum>8mandos</manvolnum></citerefentry>, which will
195
195
          normally have inherited them from
196
196
          <filename>/scripts/local-top/cryptroot</filename> in the
197
 
          initial RAM disk environment, which will have set them from
198
 
          parsing kernel arguments and
 
197
          initial <acronym>RAM</acronym> disk environment, which will
 
198
          have set them from parsing kernel arguments and
199
199
          <filename>/conf/conf.d/cryptroot</filename> (also in the
200
200
          initial RAM disk environment), which in turn will have been
201
201
          created when the initial RAM disk image was created by
240
240
      <para>
241
241
        Show a prefix before the prompt; in this case, a host name.
242
242
        It might be useful to be reminded of which host needs a
243
 
        password, in case of KVM switches, etc.
 
243
        password, in case of <acronym>KVM</acronym> switches, etc.
244
244
      </para>
245
245
      <para>
246
246
 
270
270
      >plugin-runner</refentrytitle><manvolnum>8mandos</manvolnum>
271
271
      </citerefentry>, and will, when run standalone, outside, in a
272
272
      normal environment, immediately output on its standard output
273
 
      any presumably secret password it just recieved.  Therefore,
 
273
      any presumably secret password it just received.  Therefore,
274
274
      when running this program standalone (which should never
275
275
      normally be done), take care not to type in any real secret
276
276
      password by force of habit, since it would then immediately be
290
290
    <para>
291
291
      <citerefentry><refentrytitle>crypttab</refentrytitle>
292
292
      <manvolnum>5</manvolnum></citerefentry>
293
 
      <citerefentry><refentrytitle>password-request</refentrytitle>
 
293
      <citerefentry><refentrytitle>mandos-client</refentrytitle>
294
294
      <manvolnum>8mandos</manvolnum></citerefentry>
295
295
      <citerefentry><refentrytitle>plugin-runner</refentrytitle>
296
296
      <manvolnum>8mandos</manvolnum></citerefentry>,