On Thu, Jun 06, 2002 at 02:57:28PM -0500, Steve Romero wrote:
> Didn't see a bug list, but wanted to let everyone know that I had problems
> with this beta release under the following conditions:
>
> + gcc
> + Solaris 8 (patched)
> + rsaref-2.0
> + openssl-0.9.7-beta1
>
> When compiling openssl
I just went went through this!
It may have to do with the fact that Solaris 8 and below does not have
support for random number generation.
http://wwws.sun.com/software/solaris/fcc/fcc.html
After several hours of frustration, I found some instructions that work!
I'll save you some grief:
You mu
Thank you for the help on the rand file. Next problem is
apache 2.036 with openssl 0.9.6c
../bin/apachectl startssl
[Thu Jun 06 18:20:51 2002] [crit] [Thu Jun 06 18:20:51 2002] file vhost.c, line 232,
assertion "rv == APR_SUCCESS" failed
__
Hi,
Have you found anything more on that subject.
I am interested in the result of your research.
We have 4 web servers behind a load balancer, and we receive around 200
of such message a day.
And we have no clue from where it is coming from, and how to fix it.
Gilles
> -Original Message---
Wow, it says right in your error output:
> 10175:error:24064064:random number generator:SSLEAY_RAND_BYTES:PRNG not
seeded:md_rand.c:501:You need to read the OpenSSL FAQ,
http://www.openssl.org/support/faq.html
And from the FAQ [USER] Section 1:
Pointing $RANDFILE to an Entropy Gathering Daemon
OK, I give up. What am I doing wrong? Apache 2.036 trying to on Solaris 8. Everything
seems fine during install. egd working. Random file is /var/spool/prngd/pool. Pointed
the RANDFILE at the file in openssl.conf. but keep getting the following.
I searched the archives but no luck.
./CA.sh -ne
On Thu, 6 Jun 2002, Don wrote:
> ./configure \
> --with-apxs[=/path/to/apache/bin/apxs] \
> --with-ssl=/path/to/openssl
>
> Is the first option the path to the httpd binary (httpd) or the config
> file (httpd.conf)?
Neither. It's the path to apxs. :) apxs is a script that usually sits
I tried exactly the same on RedHat 7.2, with the same result. If there is a
way round this I'd like to know as well, as for now I've given up on Apache
2.0 with RedHat 7.2.
Out of interest, is the user and group set to "apache" in the httpd.conf
file. Does the "apache" user and group exist?
Fina
Original Message
Subject: Re: Problem with: Apache/2.0.36 (Unix)
mod_ssl/2.0.36 OpenSSL/0.9.6d
Date: Tue, 04 Jun 2002 15:48:36 -0400
From: Thomas Gagné <[EMAIL PROTECTED]>
Organization: http://extra.newsguy.com
Newsgroups: comp.infosystems.www.servers.unix
References:
<[EMAI
There was a post in usenet about this issue. I'll forward one of the
last messages with some of the history. It should help.
Loren K. Louthan wrote:
> Hello,
>
> Hopefully, this will ring a bell for someone:
>
> My secure server starts up with no problem. It serves pages for 5 mins.,
> 10 min
Hello,
Hopefully, this will ring a bell for someone:
My secure server starts up with no problem. It serves pages for 5 mins.,
10 mins, sometimes even a half-hour. Eventually, however, it stops
serving pages. The clients will see "opening page *server-address* ", or
"Requesting page from *server-
Hi,
I am sorry if this question has been asked before in this group. I wanted to
find out what would be required to use private keys stored in hardware with
apache and modssl ? Modssl code looks for private key file in the host
machine and calls use_private_key() sort of function of openssl to sto
Full_Name: Luke Whitford
Version: 2.8.8
OS: Win98
Submission from: (NULL) (203.59.68.234)
When trying to start apache (1.3.24) with the mod_ssl module being loaded the
following error occurs:
C:\Program Files\Apache Group\Apache>apache
Syntax error on line 195 of c:/program files/apache
group/a
hi,
i created a CA and a ClientKey witch i imported in my Client.
in httpd.conf i configured
Alias /test/ "/opt/www/test/"
Options Indexes
Order allow,deny
Allow from 192.168.0.142
SSLVerifyClient require
SSLVerifyDepth 1
./logs/ssl_engine_log <
Hi Conrad,
I'm not very familiar with webservers yet, but you might want to use a
"virtual host"
If you let your secure host serve files from
DocumentRoot="/htdocs/secure",
and let your non-secure host serve files from
DocumentRoot="/htdocs/non-secure",
then neither of those virtual hosts can ac
On Thu, Jun 06, 2002 at 08:47:24AM +0800, Conrad Ng wrote:
> Dear all
>
> After I have implemented the SSL technology in my servers, I understand that
> users can access securely under HTTPS://. However, they can still
> access through HTTP://. Is there any way to block people from
> accessing un
16 matches
Mail list logo
