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

  • Committer: Teddy Hogeborn
  • Date: 2019-03-18 22:29:25 UTC
  • mto: This revision was merged to the branch mainline in revision 382.
  • Revision ID: teddy@recompile.se-20190318222925-jvhek84dgcfgj6g3
mandos-ctl: Refactor tests

* mandos-ctl: Where the clients names "foo" and "barbar" do not refer
              to the actual mock clients in the TestCommand class,
              change all occurrences of these names to "client1" and
              "client2" (or just "client" when only one is used) .
              Also change all test doubles to use correct terminology;
              some things called mocks are actually stubs or spies,
              and rename all true mocks to have "mock" in their names.
              Also eliminate duplicate values in tests; derive values
              from previously defined values whenever possible.

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 "2016-11-27">
 
4
<!ENTITY TIMESTAMP "2019-02-10">
5
5
<!ENTITY % common SYSTEM "common.ent">
6
6
%common;
7
7
]>
36
36
      <year>2014</year>
37
37
      <year>2015</year>
38
38
      <year>2016</year>
 
39
      <year>2017</year>
 
40
      <year>2018</year>
 
41
      <year>2019</year>
39
42
      <holder>Teddy Hogeborn</holder>
40
43
      <holder>Björn Påhlsson</holder>
41
44
    </copyright>
65
68
      The computers run a small client program in the initial RAM disk
66
69
      environment which will communicate with a server over a network.
67
70
      All network communication is encrypted using TLS.  The clients
68
 
      are identified by the server using an OpenPGP key; each client
 
71
      are identified by the server using a TLS public key; each client
69
72
      has one unique to it.  The server sends the clients an encrypted
70
73
      password.  The encrypted password is decrypted by the clients
71
 
      using the same OpenPGP key, and the password is then used to
 
74
      using a separate OpenPGP key, and the password is then used to
72
75
      unlock the root file system, whereupon the computers can
73
76
      continue booting normally.
74
77
    </para>
198
201
      <para>
199
202
        No.  The server only gives out the passwords to clients which
200
203
        have <emphasis>in the TLS handshake</emphasis> proven that
201
 
        they do indeed hold the OpenPGP private key corresponding to
202
 
        that client.
 
204
        they do indeed hold the private key corresponding to that
 
205
        client.
203
206
      </para>
204
207
    </refsect2>
205
208