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

merge

Show diffs side-by-side

added added

removed removed

Lines of Context:
plugins.d/password-prompt.xml
1
1
<?xml version="1.0" encoding="UTF-8"?>
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
<!ENTITY VERSION "1.0">
4
5
<!ENTITY COMMANDNAME "password-prompt">
5
 
<!ENTITY TIMESTAMP "2008-09-30">
6
 
<!ENTITY % common SYSTEM "../common.ent">
7
 
%common;
 
6
<!ENTITY TIMESTAMP "2008-08-31">
8
7
]>
9
8
 
10
9
<refentry xmlns:xi="http://www.w3.org/2001/XInclude">
12
11
    <title>Mandos Manual</title>
13
12
    <!-- NWalsh’s docbook scripts use this to generate the footer: -->
14
13
    <productname>Mandos</productname>
15
 
    <productnumber>&version;</productnumber>
 
14
    <productnumber>&VERSION;</productnumber>
16
15
    <date>&TIMESTAMP;</date>
17
16
    <authorgroup>
18
17
      <author>
88
87
      is not very useful on its own.  This program is really meant to
89
88
      run as a plugin in the <application>Mandos</application>
90
89
      client-side system, where it is used as a fallback and
91
 
      alternative to retrieving passwords from a <application
 
90
      alternative to retriving passwords from a <application
92
91
      >Mandos</application> server.
93
92
    </para>
94
93
    <para>
195
194
          <manvolnum>8mandos</manvolnum></citerefentry>, which will
196
195
          normally have inherited them from
197
196
          <filename>/scripts/local-top/cryptroot</filename> in the
198
 
          initial <acronym>RAM</acronym> disk environment, which will
199
 
          have set them from parsing kernel arguments and
 
197
          initial RAM disk environment, which will have set them from
 
198
          parsing kernel arguments and
200
199
          <filename>/conf/conf.d/cryptroot</filename> (also in the
201
200
          initial RAM disk environment), which in turn will have been
202
201
          created when the initial RAM disk image was created by
241
240
      <para>
242
241
        Show a prefix before the prompt; in this case, a host name.
243
242
        It might be useful to be reminded of which host needs a
244
 
        password, in case of <acronym>KVM</acronym> switches, etc.
 
243
        password, in case of KVM switches, etc.
245
244
      </para>
246
245
      <para>
247
246
 
271
270
      >plugin-runner</refentrytitle><manvolnum>8mandos</manvolnum>
272
271
      </citerefentry>, and will, when run standalone, outside, in a
273
272
      normal environment, immediately output on its standard output
274
 
      any presumably secret password it just received.  Therefore,
 
273
      any presumably secret password it just recieved.  Therefore,
275
274
      when running this program standalone (which should never
276
275
      normally be done), take care not to type in any real secret
277
276
      password by force of habit, since it would then immediately be
291
290
    <para>
292
291
      <citerefentry><refentrytitle>crypttab</refentrytitle>
293
292
      <manvolnum>5</manvolnum></citerefentry>
294
 
      <citerefentry><refentrytitle>mandos-client</refentrytitle>
 
293
      <citerefentry><refentrytitle>password-request</refentrytitle>
295
294
      <manvolnum>8mandos</manvolnum></citerefentry>
296
295
      <citerefentry><refentrytitle>plugin-runner</refentrytitle>
297
296
      <manvolnum>8mandos</manvolnum></citerefentry>,