/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: 2015-07-01 20:01:26 UTC
  • mto: This revision was merged to the branch mainline in revision 759.
  • Revision ID: teddy@recompile.se-20150701200126-qb3f6c3jcas2f4og
mandos-client: Try to start a plugin to add and remove a local route.

* debian/mandos-client.README.Debian: Add setting of environment
                                      variable MANDOSPLUGINHELPERDIR
                                      to command line testing
                                      mandos-client.
* mandos-client.c (raise_privileges): Moved to top of file.
                  (raise_privileges_permanently): - '' -
                  (lower_privileges): - '' -
                  (lower_privileges_permanently): - '' -
  (add_remove_local_route, add_local_route, remove_local_route): New.
  (start_mandos_communication): Set SOCK_CLOEXEC flag on socket.  Run
                                the above functions to add (and
                                remove) local route, if the conditions
                                indicates it could help.
  (run_network_hooks): Use O_DIRECTORY, O_PATH, and O_CLOEXEC flags
                       when opening network hook directory. Do
                       TEMP_FAILURE_RETRY around opening of /dev/null
                       and network hook executables.  Move redirecting
                       of stdout and stderr to as late as possible
                       before fexecve().
  (main): Use O_DIRECTORY and O_PATH when opening temporary directory.
* plugins.d/mandos-client.xml (ENVIRONMENT): Document usage of the
                                             MANDOSPLUGINHELPERDIR
                                             environment variable.

Show diffs side-by-side

added added

removed removed

Lines of Context:
intro.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 TIMESTAMP "2019-02-10">
 
4
<!ENTITY TIMESTAMP "2014-06-22">
5
5
<!ENTITY % common SYSTEM "common.ent">
6
6
%common;
7
7
]>
32
32
    <copyright>
33
33
      <year>2011</year>
34
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
 
      <year>2018</year>
41
 
      <year>2019</year>
42
35
      <holder>Teddy Hogeborn</holder>
43
36
      <holder>Björn Påhlsson</holder>
44
37
    </copyright>
68
61
      The computers run a small client program in the initial RAM disk
69
62
      environment which will communicate with a server over a network.
70
63
      All network communication is encrypted using TLS.  The clients
71
 
      are identified by the server using a TLS public key; each client
 
64
      are identified by the server using an OpenPGP key; each client
72
65
      has one unique to it.  The server sends the clients an encrypted
73
66
      password.  The encrypted password is decrypted by the clients
74
 
      using a separate OpenPGP key, and the password is then used to
 
67
      using the same OpenPGP key, and the password is then used to
75
68
      unlock the root file system, whereupon the computers can
76
69
      continue booting normally.
77
70
    </para>
80
73
  <refsect1 id="introduction">
81
74
    <title>INTRODUCTION</title>
82
75
    <para>
83
 
      <!-- This paragraph is a combination and paraphrase of two
84
 
           quotes from the 1995 movie “The Usual Suspects”. -->
85
76
      You know how it is.  You’ve heard of it happening.  The Man
86
77
      comes and takes away your servers, your friends’ servers, the
87
78
      servers of everybody in the same hosting facility. The servers
201
192
      <para>
202
193
        No.  The server only gives out the passwords to clients which
203
194
        have <emphasis>in the TLS handshake</emphasis> proven that
204
 
        they do indeed hold the private key corresponding to that
205
 
        client.
206
 
      </para>
207
 
    </refsect2>
208
 
    
209
 
    <refsect2 id="sniff">
210
 
      <title>How about sniffing the network traffic and decrypting it
211
 
      later by physically grabbing the Mandos client and using its
212
 
      key?</title>
213
 
      <para>
214
 
        We only use <acronym>PFS</acronym> (Perfect Forward Security)
215
 
        key exchange algorithms in TLS, which protects against this.
 
195
        they do indeed hold the OpenPGP private key corresponding to
 
196
        that client.
216
197
      </para>
217
198
    </refsect2>
218
199
    
384
365
    </para>
385
366
  </refsect1>
386
367
  
387
 
  <refsect1 id="bugs">
388
 
    <title>BUGS</title>
389
 
    <xi:include href="bugs.xml"/>
390
 
  </refsect1>
391
 
  
392
368
  <refsect1 id="see_also">
393
369
    <title>SEE ALSO</title>
394
370
    <para>
422
398
    <variablelist>
423
399
      <varlistentry>
424
400
        <term>
425
 
          <ulink url="https://www.recompile.se/mandos">Mandos</ulink>
 
401
          <ulink url="http://www.recompile.se/mandos">Mandos</ulink>
426
402
        </term>
427
403
        <listitem>
428
404
          <para>