You'll find the source RPM on the source CD for Red Hat 8.0. Install it as
any normal package (eg rpm -ivh), and you'll find the spec file that built
the binary in /usr/src/redhat/SPECS.
As Geoff points out, it is unusual that Red Hat 8.0 uses a separate package
name, but Red Hat have been doing
On Mon, Oct 28, 2002, [EMAIL PROTECTED] wrote about RE: mod_ssl-2.0.40-8:
the apache package name disappears and is called httpd instead. I guess
they are synchronising the names of the packages to match the daemon names,
although I haven't yet checked to see if bind has become named.
No, it
I wasn't just surprised, I was confused. I was looking all over for the
apache package!
I've only had a brief dabble into 8.0, but will have to consider it if and
when our apache servers start to get any heavier load. My last attempt at
Apache 2.0 ended in disaster regardless of whether I used an
Hello,
I am upgrading to the Apache Httpd 2.0 web server from 1.3.x and
cannot find any Apache-SSL package, so I'm assuming that SSL support is
now only done through mod_ssl in httpd-2.0. I compiled it with openssl
support and it appears ready to go, but I've got a question. I've got
maybe let your httpd for your non-ssl pages, and do a virtualhost on
port 443 to handle ssl pages
or one Vhost for port 80 and one Vhost for 443
Mike Smith wrote:
Hello,
I am upgrading to the Apache Httpd 2.0 web server from 1.3.x and
cannot find any Apache-SSL package, so I'm assuming
Hello All,
While trying to run apache in Windows on an Itanium (in compatibility mode
no less), I ran into the following error:
===
SSLSessionCache: Invalid argument: size has to be = 8192 bytes
===
However, the directives in question
Has anyone have any success in getting mod_speling to operate with mod_ssl
for version mod_ssl-2.8.11-1.3.27?
I configured mod_ssl with --enable-module=speling and when I do a -l on
httpd, it shows mod_speling.c is in there but whenever I place
CheckSpelling On in a virtual host, apache is
We are planning to replace an outdated copy of Stronghold (Stronghold/2.4.2
Apache/1.3.6 C2NetEU/2410) with Apache 1.3.27/mod_ssl/2.8.12.
I created what appears to be a workable httpd.conf for Apache. Accessing
http: URLS under Apache works fine. But when trying to access an
Apache/modssl https
We were able to pull off this switch this summer SH2.4.2 to Apache
1.3.x-Mod-SSL-2.8.x-OpenSSL-0.9.x
using our old certificate/keys
Grab the sources and compile, make sure you are using --with-crt
and --with-key directives correctly though. It would appear though that you
do not have something
Hi,
On Monday 28 Oct 2002 2:46 pm, Emily Eileen Witcher wrote:
We are planning to replace an outdated copy of Stronghold
(Stronghold/2.4.2 Apache/1.3.6 C2NetEU/2410) with Apache
1.3.27/mod_ssl/2.8.12.
I created what appears to be a workable httpd.conf for Apache.
Accessing http: URLS under
Hi,
Anyone know if openssl supports AES, essentially, does it support RFC
3268,
which is AES ciphersuites for TLS,
thanks,
sunitha
__
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing
Thanks - It was a missing SSLEngine On directive. I had been using the
default Apache configuration file but copied over the virtual hosts
verbatim, and Stronghold used SSLFlag On instead. Problem solved!
Emily Witcher - [EMAIL PROTECTED]
Developer and System Administrator
Crytech -
12 matches
Mail list logo