Ignore:
Timestamp:
11/11/11 13:17:43 (19 months ago)
Author:
BrainSlayer
Message:

update proftp

File:
1 edited

Legend:

Unmodified
Added
Removed
  • src/router/proftpd/doc/contrib/mod_tls.html

    r14672 r17876  
    1 <!-- $Id: mod_tls.html,v 1.26 2009/12/28 20:32:03 castaglia Exp $ --> 
     1<!-- $Id: mod_tls.html,v 1.32 2011/10/10 21:02:09 castaglia Exp $ --> 
    22<!-- $Source: /cvsroot/proftp/proftpd/doc/contrib/mod_tls.html,v $ --> 
    33 
     
    557557<p> 
    558558The <code>TLSOptions</code> directive is used to configure various optional 
    559 behavior of <code>mod_tls</code>. 
     559behavior of <code>mod_tls</code>.  <b>Note</b>: all of the configured 
     560<code>TLSOptions</code> parameters <b>must</b> appear on the same line in 
     561the configuration; only the first <code>TLSOptions</code> directive that 
     562appears in the configuration is used. 
    560563 
    561564<p> 
    562565Example: 
    563566<pre> 
    564   TLSOptions iPAddressRequired StdEnvVars 
     567  TLSOptions iPAddressRequired StdEnvVars NoSessionReuseRequired 
    565568</pre> 
    566569 
     
    572575    The <code>mod_tls</code> will reject any SSL/TLS session renegotiation 
    573576    attempts by the client, in order to mitigate any issues arising from the 
    574     <a href="http://www.educatedguesswork.org/2009/11/understanding_the_tls_renegoti.html">SSL/TLS session renegotiation vulnerability</a> (CVE-2009-3555). 
    575     If, however, your particular site or clients absolutely require support 
    576     for client-initiated SSL/TLS session renegotiations, then this option 
    577     can be used.  <b>Not recommended.</b> 
     577    <a href="http://www.educatedguesswork.org/2009/11/understanding_the_tls_renegoti.html">SSL/TLS session renegotiation vulnerability</a> (CVE-2009-3555) 
     578    or <a href="http://www.ietf.org/mail-archive/web/tls/current/msg07553.html">SSL/TLS session renegotiation DoS</a> (CVE-2011-1473).  If, however, your 
     579    particular site or clients absolutely require support for client-initiated 
     580    SSL/TLS session renegotiations, then this option can be used. 
     581    <b>Not recommended.</b> 
    578582 
    579583    <p> 
     
    628632 
    629633  <p> 
     634  <li><code>CommonNameRequired</code><br> 
     635    <p> 
     636    This option will cause <code>mod_tls</code> to perform checks on a client's 
     637    certificate once the SSL handshake has been completed: the client's 
     638    certificate will be searched for the <code>CommonName</code> (CN) X509v3 
     639    value.  Unless a <code>CommonName</code> value is present, and the 
     640    value matches the DNS name to which the client's IP address resolves, 
     641    the SSL session is closed.  This check is only performed during 
     642    SSL handshakes on the control channel.  Note that if 
     643    <code>UseReverseDNS</code> is <em>off</em>, this option is automatically 
     644    disabled. 
     645 
     646  <p> 
    630647  <li><code>EnableDiags</code><br> 
    631648    Sets callbacks in the OpenSSL library such that <b>a lot</b> of 
     
    662679    request.  This option causes the server to <b>not</b> send such a request 
    663680    during an SSL handshake. 
     681 
     682  <p> 
     683  <li><code>NoEmptyFragments</code><br> 
     684    <p> 
     685    In order to prevent certain attacks (<i>e.g.</i> the so-called 
     686    <a href="http://www.kb.cert.org/vuls/id/864643">&quotBEAST&quot; 
     687    attack</a>), the <code>mod_tls/code> module was changed to use OpenSSL's 
     688    builtin countermeasure of inserting <a href="http://www.openssl.org/~bodo/tls-cbc.txt">empty fragments</a>.  However, some browsers/clients may not handle 
     689    such empty fragments well.  Use this <code>NoEmptyFragaments</code> 
     690    TLSOption in order to interoperate with such clients, with risk of losing 
     691    the protective countermeasure. 
     692    
     693    <p> 
     694    Note that this protective countermeasure only applies to SSLv3 and TLSv1 
     695    sessions; it does not affect TLSv1.1 or TLSv1.2 sessions.  
     696 
     697    <p> 
     698    Added in ProFTPD 1.3.4rc4. 
    664699 
    665700  <p> 
     
    12751310will benefit from the speedup, but parallel simultaneous FTP connections from 
    12761311the same FTPS client will each need to perform the full SSL/TLS handshake. 
     1312By default, OpenSSL caches SSL sessions for 300 seconds (5 minutes).  If 
     1313your FTP sessions last longer than this (<i>e.g.</i> for downloading large 
     1314files), you may need to configure a longer cache lifetime using: 
     1315<pre> 
     1316  # Configure OpenSSL's internal caching to be 1800 seconds (30 minutes) 
     1317  TLSSessionCache internal: 1800 
     1318</pre> 
    12771319 
    12781320<p> 
     
    15251567  make install 
    15261568</pre> 
     1569Alternatively, <code>mod_tls</code> can be built as a DSO module: 
     1570<pre> 
     1571  ./configure --enable-dso --with-shared=mod_tls ... 
     1572</pre> 
     1573Then follow the usual steps: 
     1574<pre> 
     1575  make 
     1576  make install 
     1577</pre> 
     1578 
     1579<p> 
    15271580You may need to specify the location of the OpenSSL header and library files 
    15281581in your <code>configure</i> command, <i>e.g.</i>: 
     
    15361589<hr><br> 
    15371590Author: <i>$Author: castaglia $</i><br> 
    1538 Last Updated: <i>$Date: 2009/12/28 20:32:03 $</i><br> 
     1591Last Updated: <i>$Date: 2011/10/10 21:02:09 $</i><br> 
    15391592 
    15401593<hr> 
    15411594<font size=2><b><i> 
    1542 &copy; Copyright 2002-2009 TJ Saunders<br> 
     1595&copy; Copyright 2002-2011 TJ Saunders<br> 
    15431596 All Rights Reserved<br> 
    15441597</i></b></font> 
Note: See TracChangeset for help on using the changeset viewer.