/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: 2012-05-12 15:45:57 UTC
  • Revision ID: teddy@recompile.se-20120512154557-r1yzcb8su8byp4us
* mandos (Client.enable, Client.disable, ClientDBus.approve): Call
                    self.send_changedstate() after change, not before.
  (Client.disable): Bug fix: Handle disable_initiator_tag and
                    checker_initiator_tag of 0.
  (Client.init_checker): Bug fix: Remove old checker_initiator_tag and
                         disable_initiator_tag, if any.
  (Client.bump_timeout): Bug fix: Remove old disable_initiator_tag, if
                         any.
  (ClientDBus.Timeout_dbus_property): Bug fix: Use self.expires.
  (ClientHandler.handle): Bug fix: timedelta_to_milliseconds is a
                          global function, not a class method.
* mandos-monitor (MandosClientWidget._update_timer_callback_lock):
  Removed.  All users changed.
  (MandosClientWidget.last_checked_ok): Removed (unused).
  (MandosClientWidget.__init__): Don't call self.using_timer().
  (MandosClientWidget.property_changed): Removed unused version.
  (MandosClientWidget.using_timer): Stop using the counter
                                    self._update_timer_callback_lock;
                                    be strictly boolean.
  (MandosClientWidget.need_approval): Don't call self.using_timer().
  (MandosClientWidget.update): Call self.using_timer() throughout.
                               Bug fix: Never show negative timers.

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-03-22">
 
4
<!ENTITY TIMESTAMP "2012-01-01">
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
35
      <holder>Teddy Hogeborn</holder>
40
36
      <holder>Björn Påhlsson</holder>
41
37
    </copyright>
201
197
      </para>
202
198
    </refsect2>
203
199
    
204
 
    <refsect2 id="sniff">
205
 
      <title>How about sniffing the network traffic and decrypting it
206
 
      later by physically grabbing the Mandos client and using its
207
 
      key?</title>
208
 
      <para>
209
 
        We only use <acronym>PFS</acronym> (Perfect Forward Security)
210
 
        key exchange algorithms in TLS, which protects against this.
211
 
      </para>
212
 
    </refsect2>
213
 
    
214
200
    <refsect2 id="physgrab">
215
201
      <title>Physically grabbing the Mandos server computer?</title>
216
202
      <para>
229
215
      </para>
230
216
    </refsect2>
231
217
    
232
 
    <refsect2 id="fakecheck">
233
 
      <title>Faking checker results?</title>
 
218
    <refsect2 id="fakeping">
 
219
      <title>Faking ping replies?</title>
234
220
      <para>
235
 
        If the Mandos client does not have an SSH server, the default
236
 
        is for the Mandos server to use
 
221
        The default for the server is to use
237
222
        <quote><literal>fping</literal></quote>, the replies to which
238
223
        could be faked to eliminate the timeout.  But this could
239
224
        easily be changed to any shell command, with any security
240
 
        measures you like.  If the Mandos client
241
 
        <emphasis>has</emphasis> an SSH server, the default
242
 
        configuration (as generated by
243
 
        <command>mandos-keygen</command> with the
244
 
        <option>--password</option> option) is for the Mandos server
245
 
        to use an <command>ssh-keyscan</command> command with strict
246
 
        keychecking, which can not be faked.  Alternatively, IPsec
247
 
        could be used for the ping packets, making them secure.
 
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.
248
229
      </para>
249
230
    </refsect2>
250
231
  </refsect1>
379
360
    </para>
380
361
  </refsect1>
381
362
  
382
 
  <refsect1 id="bugs">
383
 
    <title>BUGS</title>
384
 
    <xi:include href="bugs.xml"/>
385
 
  </refsect1>
386
 
  
387
363
  <refsect1 id="see_also">
388
364
    <title>SEE ALSO</title>
389
365
    <para>
417
393
    <variablelist>
418
394
      <varlistentry>
419
395
        <term>
420
 
          <ulink url="https://www.recompile.se/mandos">Mandos</ulink>
 
396
          <ulink url="http://www.recompile.se/mandos">Mandos</ulink>
421
397
        </term>
422
398
        <listitem>
423
399
          <para>