Other references : OSVDB:6472
Upgrading to newer mod_ssl version involves lot of effort. So we are
looking for 2.8.16 patches.
Where are the 2.8.16 patches for above bugs?.
Thanks for your assistance.
Madhu K.S.
The information contained in this electronic message and any attachments to
this
> Cool..
> Can you please post the patch to the list, so that ppl can review the
> code,
> and give their comments.
> -Madhu
No problem!
Here is my short README describing the patch and its history form Apache
version 2.0.43 to 2.0.44:
Hello!
This is the distribution point for the Apache 2.0 as
patched that and now I
can see the intermediate CAs as SSL_CLIENT_CERT_CHAIN_0 to
SSL_CLIENT_CERT_CHAIN_n in the environment.
Last but not least I have updated the mod_headers documentation with the new
option "E" and an example for forwarding the Web browser's client
certificate and some o
e version 1.3.12
>2. rsaref version 2.0
>3. openssl version 0.9.5
>4. mm version 1.0.12
>5. mod_ssl version 2.6.2-1.3.12
>
>After all this, I am trying to apply the mod_ssl source extension and source
>patches to the Apache source tree with the following command, it is
e version 1.3.12
>2. rsaref version 2.0
>3. openssl version 0.9.5
>4. mm version 1.0.12
>5. mod_ssl version 2.6.2-1.3.12
>
>After all this, I am trying to apply the mod_ssl source extension and source
>patches to the Apache source tree with the following command, it is
version 2.6.2-1.3.12
After all this, I am trying to apply the mod_ssl source extension and source
patches to the Apache source tree with the following command, it is shooting the
following error. Could you help me.
./configure \
> --with-apache=../apache_1.3.12 \
> --with-ssl=../openssl
Le mar, 09 fév 1999, vous avez écrit :
>On Tue, Feb 09, 1999, [EMAIL PROTECTED] wrote:
>
>> I think I got one bug with mod_ssl distrib 2.2.0 and 2.2.2.
>> When I run mod_ssl's configure, it ends with "patches applyed succesfully" but
>> some errors have cre
On Tue, Feb 09, 1999, [EMAIL PROTECTED] wrote:
> I think I got one bug with mod_ssl distrib 2.2.0 and 2.2.2.
> When I run mod_ssl's configure, it ends with "patches applyed succesfully" but
> some errors have created *.rej files. The problem is that I am never get
&g
Hi,
I think I got one bug with mod_ssl distrib 2.2.0 and 2.2.2.
When I run mod_ssl's configure, it ends with "patches applyed succesfully" but
some errors have created *.rej files. The problem is that I am never get
notified of those errors.
--
Ronan-Yann Lorin
On Thu, Sep 24, 1998, Tom Vaughan wrote:
> > Wait! I didn't mean that you can rsync only the HEAD stuff. You can rsync the
> > complete CVS repository with the ,v files. Here RSync is better than
> > Real-CVS, because RSync is faster in updating your local repository copy and
> > then you have
> Wait! I didn't mean that you can rsync only the HEAD stuff. You can rsync the
> complete CVS repository with the ,v files. Here RSync is better than
> Real-CVS, because RSync is faster in updating your local repository copy and
> then you have the advantage of fast checkout/diff/update operati
Tom Vaughan wrote:
> But:
>
> $ rsync -rztpv --delete sw.engelschall.com::mod_ssl-distrib \
> /tmp/mod_ssl
>
> fails. Strace reports that I'm stuck in a loop waiting on select. Is this
> just me, or have others had problems?
I'm using
10 3,15 * * * /usr/bin/rsync -rztpv s
In article <> you wrote:
>> Ok, I'll see what I can do for you and others who want such access. What is
>> your preferred access method? Plain (Anon-)CVS? CVSup? RSYNC? Whatever? The
>> sw.engelschall.com machine at the ETHZ is a Solaris box, so CVSup is horrible
>> to install (Modula-3!), Anon-
> Ok, I'll see what I can do for you and others who want such access. What is
> your preferred access method? Plain (Anon-)CVS? CVSup? RSYNC? Whatever? The
> sw.engelschall.com machine at the ETHZ is a Solaris box, so CVSup is horrible
> to install (Modula-3!), Anon-CVS is ok but required a littl
In article <> you wrote:
>> Inside pkg.mod_ssl the mod_ssl distribution stays, inside pkg.ssleay the
>> SSLeay versions stay and inside pkg.apache is what you want: Apache releases
>> (currently 1.3.1) on the vendor branch and Apache+mod_ssl on the HEAD (inside
>> admin/ there are config files an
> Inside pkg.mod_ssl the mod_ssl distribution stays, inside pkg.ssleay the
> SSLeay versions stay and inside pkg.apache is what you want: Apache releases
> (currently 1.3.1) on the vendor branch and Apache+mod_ssl on the HEAD (inside
> admin/ there are config files and scripts to assemble pkg.mod_
16 matches
Mail list logo
