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

  • Committer: Teddy Hogeborn
  • Date: 2011-11-26 22:22:20 UTC
  • mto: (518.1.8 mandos-persistent)
  • mto: This revision was merged to the branch mainline in revision 524.
  • Revision ID: teddy@recompile.se-20111126222220-1ubwjpb5ugqnrhec
Directory with persistent state can now be changed with the "statedir"
option.  The state directory /var/lib/mandos now gets created on
installation.  Added documentation about "restore" and "statedir"
options.

* Makefile (USER, GROUP, STATEDIR): New.
  (maintainer-clean): Also remove "statedir".
  (run-server): Replaced "--no-restore" with "--statedir=statedir".
  (statedir): New.
  (install-server): Make $(STATEDIR) directory.
* debian/mandos.dirs (var/lib/mandos): Added.
* debian/mandos.postinst: Fix ownership of /var/lib/mandos.
* mandos: New --statedir option.
  (stored_state_path): Not global anymore.
  (stored_state_file): New global.
* mandos.conf: Fix whitespace.
  (restore, statedir): Added.
* mandos.conf.xml (OPTIONS, EXAMPLE): Added "restore" and "statedir".
  mandos.xml (SYNOPSIS, OPTIONS): Added "--statedir".
  (FILES): Added "/var/lib/mandos".

Show diffs side-by-side

added added

removed removed

Lines of Context:
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 TIMESTAMP "2017-02-23">
 
4
<!ENTITY TIMESTAMP "2011-10-03">
5
5
<!ENTITY % common SYSTEM "common.ent">
6
6
%common;
7
7
]>
31
31
    </authorgroup>
32
32
    <copyright>
33
33
      <year>2011</year>
34
 
      <year>2012</year>
35
 
      <year>2013</year>
36
 
      <year>2014</year>
37
 
      <year>2015</year>
38
 
      <year>2016</year>
39
 
      <year>2017</year>
40
34
      <holder>Teddy Hogeborn</holder>
41
35
      <holder>Björn Påhlsson</holder>
42
36
    </copyright>
78
72
  <refsect1 id="introduction">
79
73
    <title>INTRODUCTION</title>
80
74
    <para>
81
 
      <!-- This paragraph is a combination and paraphrase of two
82
 
           quotes from the 1995 movie “The Usual Suspects”. -->
83
75
      You know how it is.  You’ve heard of it happening.  The Man
84
76
      comes and takes away your servers, your friends’ servers, the
85
77
      servers of everybody in the same hosting facility. The servers
204
196
      </para>
205
197
    </refsect2>
206
198
    
207
 
    <refsect2 id="sniff">
208
 
      <title>How about sniffing the network traffic and decrypting it
209
 
      later by physically grabbing the Mandos client and using its
210
 
      key?</title>
211
 
      <para>
212
 
        We only use <acronym>PFS</acronym> (Perfect Forward Security)
213
 
        key exchange algorithms in TLS, which protects against this.
214
 
      </para>
215
 
    </refsect2>
216
 
    
217
199
    <refsect2 id="physgrab">
218
200
      <title>Physically grabbing the Mandos server computer?</title>
219
201
      <para>
232
214
      </para>
233
215
    </refsect2>
234
216
    
235
 
    <refsect2 id="fakecheck">
236
 
      <title>Faking checker results?</title>
 
217
    <refsect2 id="fakeping">
 
218
      <title>Faking ping replies?</title>
237
219
      <para>
238
 
        If the Mandos client does not have an SSH server, the default
239
 
        is for the Mandos server to use
 
220
        The default for the server is to use
240
221
        <quote><literal>fping</literal></quote>, the replies to which
241
222
        could be faked to eliminate the timeout.  But this could
242
223
        easily be changed to any shell command, with any security
243
 
        measures you like.  If the Mandos client
244
 
        <emphasis>has</emphasis> an SSH server, the default
245
 
        configuration (as generated by
246
 
        <command>mandos-keygen</command> with the
247
 
        <option>--password</option> option) is for the Mandos server
248
 
        to use an <command>ssh-keyscan</command> command with strict
249
 
        keychecking, which can not be faked.  Alternatively, IPsec
250
 
        could be used for the ping packets, making them secure.
 
224
        measures you like.  It could, for instance, be changed to an
 
225
        SSH command with strict keychecking, which could not be faked.
 
226
        Or IPsec could be used for the ping packets, making them
 
227
        secure.
251
228
      </para>
252
229
    </refsect2>
253
230
  </refsect1>
382
359
    </para>
383
360
  </refsect1>
384
361
  
385
 
  <refsect1 id="bugs">
386
 
    <title>BUGS</title>
387
 
    <xi:include href="bugs.xml"/>
388
 
  </refsect1>
389
 
  
390
362
  <refsect1 id="see_also">
391
363
    <title>SEE ALSO</title>
392
364
    <para>
420
392
    <variablelist>
421
393
      <varlistentry>
422
394
        <term>
423
 
          <ulink url="https://www.recompile.se/mandos">Mandos</ulink>
 
395
          <ulink url="http://www.recompile.se/mandos">Mandos</ulink>
424
396
        </term>
425
397
        <listitem>
426
398
          <para>