/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: 2013-12-14 03:11:30 UTC
  • mto: (237.7.272 trunk)
  • mto: This revision was merged to the branch mainline in revision 307.
  • Revision ID: teddy@recompile.se-20131214031130-xicrtjuxxttgqazf
http://bugs.debian.org/731618
Switch from avahi to avahi-daemon in initscript LSB dependencies

* init.d-mandos (Required-Start, Required-Stop):
  Change "avahi" to "avahi-daemon".

Reported-by: Laurent Bigonville <bigon@debian.org>
Suggested-by: Laurent Bigonville <bigon@debian.org>

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 "2012-01-01">
5
5
<!ENTITY % common SYSTEM "common.ent">
6
6
%common;
7
7
]>
215
215
      </para>
216
216
    </refsect2>
217
217
    
218
 
    <refsect2 id="fakecheck">
219
 
      <title>Faking checker results?</title>
 
218
    <refsect2 id="fakeping">
 
219
      <title>Faking ping replies?</title>
220
220
      <para>
221
 
        If the Mandos client does not have an SSH server, the default
222
 
        is for the Mandos server to use
 
221
        The default for the server is to use
223
222
        <quote><literal>fping</literal></quote>, the replies to which
224
223
        could be faked to eliminate the timeout.  But this could
225
224
        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.
 
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.
234
229
      </para>
235
230
    </refsect2>
236
231
  </refsect1>