Mailing-List: contact community-help@apache.org; run by ezmlm
Precedence: bulk
Reply-To: community@apache.org
Received-SPF: pass (athena.apache.org: domain of sebbaz@gmail.com designates
 209.85.220.178 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=W2AnyIPy30K+Aw89RYr3IHroQ5wX3bET/nJDresU9pmAIc21awGaftT8+v5qKQ3GA9
         +qq/lZAXvCF/cBpMBykHY5+Si+PrOsY0XJw1b91eYNkIp/w/GixeqvenhcKq29Fh70p2
         FZOWFYwLFjkowBQRb6hJPjMAT5E6Qzu1w3S7s=
MIME-Version: 1.0
In-Reply-To: <BANLkTikWCSDOdXA1Pr6Ln7-GCQzhpeCnRw@mail.gmail.com>
References: <BANLkTikWCSDOdXA1Pr6Ln7-GCQzhpeCnRw@mail.gmail.com>
Date: Sat, 9 Apr 2011 23:33:20 +0100
Message-ID: <BANLkTinerOb8fRk6RH=o4QUgHidUekRvfA@mail.gmail.com>
Subject: Re: Disabling client initiated renegotiation
From: sebb <sebbaz@gmail.com>
To: community@apache.org
Content-Type: text/plain; charset=ISO-8859-1

On 9 April 2011 22:48, Chris Hill <chris.hillsec@gmail.com> wrote:
> Hi all,
>
> My company relies on Apache for a number of customer facing sites. What's a
> reliable way to disable client initiated renegotiation (both secure and
> insecure renegotiation)?. I know one specific openssl library (l) disables
> this, but then later ones enable "secure" renegotiation, which we need to
> disable.
>
> Ideally, I'd like a solution through an configuration parameter so that
> future versions/upgrades do not re-enable renegotiation.

If you are referring to Apache httpd, that sounds like a question for
the httpd user mailing list [A].

Or if you are using Apache Tomcat, its user list [T] is the place to
ask such questions.


[A] http://httpd.apache.org/lists.html

[T] http://tomcat.apache.org/lists.html

---------------------------------------------------------------------
To unsubscribe, e-mail: community-unsubscribe@apache.org
For additional commands, e-mail: community-help@apache.org