/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-08-10 07:34:37 UTC
  • Revision ID: teddy@recompile.se-20150810073437-3m8jgt13nqric6vf
Revert change to D-Bus API.

The D-Bus API signal CheckerCompleted is documented to provide a
wait(2) status value.  Since the server switched to using subprocess
to run checkers, it no longer has access to a wait(2) status value.  A
previous change to work around this made the D-Bus API incompatible.
Revert this change by constructing a fake wait(2) status value; this
keeps the D-Bus API stable.

* DBUS-API (CheckerCompleted): Revert incompatible change.
* mandos (ClientDBus.checker_callback): Construct fake wait(2) status.
* mandos-monitor (MandosClientWidget.checker_completed): Revert to
                                                         using
                                                         original API
                                                         with wait(2)
                                                         condition
                                                         value.

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 "2012-01-01">
 
4
<!ENTITY TIMESTAMP "2015-07-20">
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>
35
38
      <holder>Teddy Hogeborn</holder>
36
39
      <holder>Björn Påhlsson</holder>
37
40
    </copyright>
197
200
      </para>
198
201
    </refsect2>
199
202
    
 
203
    <refsect2 id="sniff">
 
204
      <title>How about sniffing the network traffic and decrypting it
 
205
      later by physically grabbing the Mandos client and using its
 
206
      key?</title>
 
207
      <para>
 
208
        We only use <acronym>PFS</acronym> (Perfect Forward Security)
 
209
        key exchange algorithms in TLS, which protects against this.
 
210
      </para>
 
211
    </refsect2>
 
212
    
200
213
    <refsect2 id="physgrab">
201
214
      <title>Physically grabbing the Mandos server computer?</title>
202
215
      <para>
215
228
      </para>
216
229
    </refsect2>
217
230
    
218
 
    <refsect2 id="fakeping">
219
 
      <title>Faking ping replies?</title>
 
231
    <refsect2 id="fakecheck">
 
232
      <title>Faking checker results?</title>
220
233
      <para>
221
 
        The default for the server is to use
 
234
        If the Mandos client does not have an SSH server, the default
 
235
        is for the Mandos server to use
222
236
        <quote><literal>fping</literal></quote>, the replies to which
223
237
        could be faked to eliminate the timeout.  But this could
224
238
        easily be changed to any shell command, with any security
225
 
        measures you like.  It could, for instance, be changed to an
226
 
        SSH command with strict keychecking, which could not be faked.
227
 
        Or IPsec could be used for the ping packets, making them
228
 
        secure.
 
239
        measures you like.  If the Mandos client
 
240
        <emphasis>has</emphasis> an SSH server, the default
 
241
        configuration (as generated by
 
242
        <command>mandos-keygen</command> with the
 
243
        <option>--password</option> option) is for the Mandos server
 
244
        to use an <command>ssh-keyscan</command> command with strict
 
245
        keychecking, which can not be faked.  Alternatively, IPsec
 
246
        could be used for the ping packets, making them secure.
229
247
      </para>
230
248
    </refsect2>
231
249
  </refsect1>