/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 mandos-options.xml

  • Committer: Teddy Hogeborn
  • Date: 2019-02-10 03:50:20 UTC
  • mto: (237.7.594 trunk)
  • mto: This revision was merged to the branch mainline in revision 370.
  • Revision ID: teddy@recompile.se-20190210035020-nttr1tybgwwixueu
http://bugs.debian.org/879538
http://bugs.debian.org/916673
Show debconf note about new TLS key IDs

If mandos-client did not see TLS keys and had to create them, or if
mandos sees GnuTLS version 3.6.6 or later, show an important notice on
package installation about the importance of adding the new key_id
options to clients.conf on the Mandos server.

* debian/control (Package: mandos, Package: mandos-client): Depend on
                                                            debconf.
* debian/mandos-client.lintian-overrides: Override warnings.
* debian/mandos-client.postinst (create_keys): Show notice if new TLS
                                               key files were created.
* debian/mandos-client.templates: New.
* debian/mandos.lintian-overrides: Override warnings.
* debian/mandos.postinst (configure): If GnuTLS 3.6.6 or later is
                                      detected, show an important
                                      notice (once) about the new
                                      key_id option required in
                                      clients.conf.
* debian/mandos.templates: New.

Show diffs side-by-side

added added

removed removed

Lines of Context:
mandos-options.xml
46
46
    <emphasis>not</emphasis> run in debug mode.
47
47
  </para>
48
48
  
49
 
  <para id="priority_compat">
 
49
  <para id="priority">
50
50
    GnuTLS priority string for the <acronym>TLS</acronym> handshake.
51
 
    The default is <quote><literal
52
 
    >SECURE256:!CTYPE-X.509:+CTYPE-OPENPGP:+SIGN-RSA-SHA224:</literal>
53
 
    <literal>+SIGN-RSA-RMD160</literal></quote>.
54
 
    See <citerefentry><refentrytitle
 
51
    The default is
 
52
    <quote><literal>SECURE128&#8203;:!CTYPE-X.509&#8203;:+CTYPE-RAWPK&#8203;:!RSA&#8203;:!VERS-ALL&#8203;:+VERS-TLS1.3&#8203;:%PROFILE_ULTRA</literal></quote>
 
53
    when using raw public keys in TLS, and
 
54
    <quote><literal>SECURE256&#8203;:!CTYPE-X.509&#8203;:+CTYPE-OPENPGP&#8203;:!RSA&#8203;:+SIGN-DSA-SHA256</literal></quote>
 
55
    when using OpenPGP keys in TLS,.  See <citerefentry><refentrytitle
55
56
    >gnutls_priority_init</refentrytitle>
56
57
    <manvolnum>3</manvolnum></citerefentry> for the syntax.
57
58
    <emphasis>Warning</emphasis>: changing this may make the
58
59
    <acronym>TLS</acronym> handshake fail, making server-client
59
 
    communication impossible.
60
 
  </para>
61
 
  
62
 
  <para id="priority">
63
 
    GnuTLS priority string for the <acronym>TLS</acronym> handshake.
64
 
    The default is <quote><literal
65
 
    >SECURE256:!CTYPE-X.509:+CTYPE-OPENPGP</literal></quote>.  See
66
 
    <citerefentry><refentrytitle >gnutls_priority_init</refentrytitle>
67
 
    <manvolnum>3</manvolnum></citerefentry> for the syntax.
68
 
    <emphasis>Warning</emphasis>: changing this may make the
69
 
    <acronym>TLS</acronym> handshake fail, making server-client
70
 
    communication impossible.
 
60
    communication impossible.  Changing this option may also make the
 
61
    network traffic decryptable by an attacker.
71
62
  </para>
72
63
  
73
64
  <para id="servicename">
123
114
    implies this option.
124
115
  </para>
125
116
  
 
117
  <para id="zeroconf">
 
118
    This option controls whether the server will announce its
 
119
    existence using Zeroconf.  Default is to use Zeroconf.  If
 
120
    Zeroconf is not used, a <option>port</option> number or a
 
121
    <option>socket</option> is required.
 
122
  </para>
 
123
  
126
124
</section>