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

  • Committer: Teddy Hogeborn
  • Date: 2008-09-12 19:12:40 UTC
  • Revision ID: teddy@fukt.bsnet.se-20080912191240-edjlcll43eoijkx0
* Makefile (install): Use "install-client-nokey".
  (install-server): Create "/etc/default" and "/usr/sbin", too.
  (install-client): Do not depend on "$(INITRAMFSTOOLS)/hooks/.".
                    Renamed to "install-client-nokey".  Split out
                    post-installation-stuff to new "install-client"
                    target.

* mandos-clients.conf.xml: White space adjustments.
* mandos-keygen.xml: - '' -
* mandos.conf.xml: - '' -
* mandos.xml: - '' -
* plugin-runner.xml: - '' -
* plugins.d/mandos-client.xml: - '' -

* overview.xml: Improved grammar.

Show diffs side-by-side

added added

removed removed

Lines of Context:
mandos.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 "mandos">
5
 
<!ENTITY TIMESTAMP "2008-10-03">
6
 
<!ENTITY % common SYSTEM "common.ent">
7
 
%common;
 
6
<!ENTITY TIMESTAMP "2008-09-12">
8
7
]>
9
8
 
10
9
<refentry xmlns:xi="http://www.w3.org/2001/XInclude">
11
 
   <refentryinfo>
 
10
  <refentryinfo>
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>
351
350
    </variablelist>
352
351
  </refsect1>
353
352
  
354
 
  <refsect1 id="files">
 
353
  <refsect1 id="file">
355
354
    <title>FILES</title>
356
355
    <para>
357
356
      Use the <option>--configdir</option> option to change where
421
420
      Currently, if a client is declared <quote>invalid</quote> due to
422
421
      having timed out, the server does not record this fact onto
423
422
      permanent storage.  This has some security implications, see
424
 
      <xref linkend="clients"/>.
 
423
      <xref linkend="CLIENTS"/>.
425
424
    </para>
426
425
    <para>
427
426
      There is currently no way of querying the server of the current
483
482
  
484
483
  <refsect1 id="security">
485
484
    <title>SECURITY</title>
486
 
    <refsect2 id="server">
 
485
    <refsect2 id="SERVER">
487
486
      <title>SERVER</title>
488
487
      <para>
489
488
        Running this <command>&COMMANDNAME;</command> server program
492
491
        soon after startup.
493
492
      </para>
494
493
    </refsect2>
495
 
    <refsect2 id="clients">
 
494
    <refsect2 id="CLIENTS">
496
495
      <title>CLIENTS</title>
497
496
      <para>
498
497
        The server only gives out its stored data to clients which
505
504
        <citerefentry><refentrytitle>mandos-clients.conf</refentrytitle>
506
505
        <manvolnum>5</manvolnum></citerefentry>)
507
506
        <emphasis>must</emphasis> be made non-readable by anyone
508
 
        except the user starting the server (usually root).
 
507
        except the user running the server.
509
508
      </para>
510
509
      <para>
511
510
        As detailed in <xref linkend="checking"/>, the status of all