/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 plugins.d/mandos-client.xml

  • Committer: Teddy Hogeborn
  • Date: 2014-07-25 23:54:03 UTC
  • Revision ID: teddy@recompile.se-20140725235403-8sx708g7rosge1ei
Bug fix to allow Python 3; that is, version 3 of the "python" package.

* debian/control (Package: mandos/Depends): Bug fix: Change from
                                            "python (<= 2.7)" to
                                            "python (>= 2.7)",
                                            allowing "/usr/bin/python"
                                            to be Python 3.

Show diffs side-by-side

added added

removed removed

Lines of Context:
plugins.d/mandos-client.xml
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
4
<!ENTITY COMMANDNAME "mandos-client">
5
 
<!ENTITY TIMESTAMP "2012-07-23">
 
5
<!ENTITY TIMESTAMP "2014-06-22">
6
6
<!ENTITY % common SYSTEM "../common.ent">
7
7
%common;
8
8
]>
34
34
      <year>2008</year>
35
35
      <year>2009</year>
36
36
      <year>2012</year>
 
37
      <year>2013</year>
 
38
      <year>2014</year>
37
39
      <holder>Teddy Hogeborn</holder>
38
40
      <holder>Björn Påhlsson</holder>
39
41
    </copyright>
218
220
            assumed to separate the address from the port number.
219
221
          </para>
220
222
          <para>
221
 
            This option is normally only useful for testing and
222
 
            debugging.
 
223
            Normally, Zeroconf would be used to locate Mandos servers,
 
224
            in which case this option would only be used when testing
 
225
            and debugging.
223
226
          </para>
224
227
        </listitem>
225
228
      </varlistentry>
258
261
          <para>
259
262
            <replaceable>NAME</replaceable> can be the string
260
263
            <quote><literal>none</literal></quote>; this will make
261
 
            <command>&COMMANDNAME;</command> not bring up
262
 
            <emphasis>any</emphasis> interfaces specified
263
 
            <emphasis>after</emphasis> this string.  This is not
264
 
            recommended, and only meant for advanced users.
 
264
            <command>&COMMANDNAME;</command> only bring up interfaces
 
265
            specified <emphasis>before</emphasis> this string.  This
 
266
            is not recommended, and only meant for advanced users.
265
267
          </para>
266
268
        </listitem>
267
269
      </varlistentry>
666
668
    </para>
667
669
    <informalexample>
668
670
      <para>
669
 
        Normal invocation needs no options, if the network interface
 
671
        Normal invocation needs no options, if the network interfaces
670
672
        can be automatically determined:
671
673
      </para>
672
674
      <para>
675
677
    </informalexample>
676
678
    <informalexample>
677
679
      <para>
678
 
        Search for Mandos servers (and connect to them) using another
679
 
        interface:
 
680
        Search for Mandos servers (and connect to them) using one
 
681
        specific interface:
680
682
      </para>
681
683
      <para>
682
684
        <!-- do not wrap this line -->
746
748
    <para>
747
749
      It will also help if the checker program on the server is
748
750
      configured to request something from the client which can not be
749
 
      spoofed by someone else on the network, unlike unencrypted
750
 
      <acronym>ICMP</acronym> echo (<quote>ping</quote>) replies.
 
751
      spoofed by someone else on the network, like SSH server key
 
752
      fingerprints, and unlike unencrypted <acronym>ICMP</acronym>
 
753
      echo (<quote>ping</quote>) replies.
751
754
    </para>
752
755
    <para>
753
756
      <emphasis>Note</emphasis>: This makes it completely insecure to