/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

* plugins.d/mandos-client.c (good_interface): Use SIOCGIFFLAGS instead
                                              of reading
                                              /sys/class/net/*/flags.

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 "2014-06-22">
 
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
34
      <holder>Teddy Hogeborn</holder>
36
35
      <holder>Björn Påhlsson</holder>
37
36
    </copyright>
215
214
      </para>
216
215
    </refsect2>
217
216
    
218
 
    <refsect2 id="fakecheck">
219
 
      <title>Faking checker results?</title>
 
217
    <refsect2 id="fakeping">
 
218
      <title>Faking ping replies?</title>
220
219
      <para>
221
 
        If the Mandos client does not have an SSH server, the default
222
 
        is for the Mandos server to use
 
220
        The default for the server is to use
223
221
        <quote><literal>fping</literal></quote>, the replies to which
224
222
        could be faked to eliminate the timeout.  But this could
225
223
        easily be changed to any shell command, with any security
226
 
        measures you like.  If the Mandos client
227
 
        <emphasis>has</emphasis> an SSH server, the default
228
 
        configuration (as generated by
229
 
        <command>mandos-keygen</command> with the
230
 
        <option>--password</option> option) is for the Mandos server
231
 
        to use an <command>ssh-keyscan</command> command with strict
232
 
        keychecking, which can not be faked.  Alternatively, IPsec
233
 
        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.
234
228
      </para>
235
229
    </refsect2>
236
230
  </refsect1>