/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: 2014-06-08 03:10:08 UTC
  • mto: (237.7.272 trunk)
  • mto: This revision was merged to the branch mainline in revision 317.
  • Revision ID: teddy@recompile.se-20140608031008-mc9bd7b024a3q0y0
Address a very theoretical possible security issue in mandos-client.

If there were to run some sort of "cleaner" process for /run/tmp (or
/tmp), and mandos-client were to run for long enough for that cleaner
process to remove the temporary directory for GPGME, there was a
possibility that another unprivileged process could trick the (also
unprivileged) mandos-client process to remove other files or symlinks
which the unprivileged mandos-client process was allowed to remove.
This is not currently known to have been exploitable, since there are
no known initramfs environments running such cleaner processes.

* plugins.d/mandos-client.c (main): Use O_NOFOLLOW when opening
                                    tempdir for cleaning.

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