Thanks for the response, but it seems you've misunderstood me.
Now, I took a look at the certs, I noticed that all of them
start with "-BEGIN X509 CERTIFICATE-". When I originally
got these from Thawte, the header was "-BEGIN CERTIFICATE-".
Yes, OpenSSL looks for "BEGIN
You would have to reference all the images with the full url name.
For example, if youur page is
https://mydomain.com/index.html
All your graphics on the page would have to be
http://mydomain.com/graphic1.gif
https:// ...
^
;)
mh
instead of just /graphic1.gif
Of
On Mon, Sep 27, 1999, WSO Support wrote:
[...]
The *new* cert I have from Thawte starts with just
"-BEGIN CERTIFICATE-", as all of the others I have ever
gotten in the past from Thawte. The only difference now is that
this is a v3 cert, not v1, as all these others were.
You
Full_Name:
Version: 2.4.3
OS: Slackware-current
Submission from: (NULL) (194.106.159.74)
when using the "The flexible APACI-only way", everything works fine until here:
=== src/modules/ssl
gcc -c -I../../os/unix -I../../include -DLINUX=2 -DMOD_SSL=204103
-DUSE_HSREGEX -DEAPI -DUSE_EXPAT
Hi,
Have followed all the various docs on installs and I get various
results, except https working.
First attempt compiled and ran ok, according to the ssl_engine.log
which finishes by saying Configuring server ...for SSL protocol.
However: openssl gives an error 16.
also curl says https is
The following patch fixes the error which occurs when using
make certificate VIEW=1
to display the certificate and key. Currently, it ends in..
./support/mkcert.sh: : cannot execute
./support/mkcert.sh: test: unknown operator Algorithm | grep -i RSA
Make[1]: *** [certificate] Error 1
Make[1]:
As you know, shit happens, so the enabled IPC semaphore support from 2.4.3 for
xBSD, Solaris and Linux was broken under compile time for Linux where `union
semun' is (correctly) not pre-defined. So we need mod_ssl 2.4.4 which
immediately fixes this nasty compilation problem for the Linux
Oops -- I fixed only one of them locations. Here's an updated patch.
Martin
--
[EMAIL PROTECTED] |Siemens Information and
Phone: +49-89-636-46021 |Communication Products
FAX: +49-89-636-47816 |81730 Munich, Germany
***
On Tue, Sep 28, 1999, [EMAIL PROTECTED] wrote:
Full_Name:
Version: 2.4.3
OS: Slackware-current
Submission from: (NULL) (194.106.159.74)
when using the "The flexible APACI-only way", everything works fine until here:
=== src/modules/ssl
gcc -c -I../../os/unix -I../../include
Full_Name:
Version: 2.4.4
OS: Slackware-current
Submission from: dns0.prestoncoll.ac.uk (194.238.8.2)
hmm, very related to bug 291!
when using the "The flexible APACI-only way", everything works fine until here:
=== src/modules/ssl
gcc -c -I../../os/unix -I../../include -DLINUX=2
2.4.3 compiled OK on my redhat 5.2 box, but 2.4.4 barfs:
gcc -c -I../../../../mm-1.0.11 -I../../os/unix -I../../include -O2 -m486
-fno-strength-reduce
-DLINUX=2 -DMOD_SSL=204104 -DEAPI -DEAPI_MM -DUSE_EXPAT -I../../lib/expat-lite
`../../apaci` -fpic
-DSHARED_MODULE -DSSL_COMPAT -I/usr/include
I am back...
Cristi's patch and the 2.4.4 release solved my compile problem.
However, when I build using APXS, I still cannot properly link at
run-time:
Cannot load /usr/local/apache/libexec/libssl.so into server:
/usr/local/apache/libexec/libssl.so: undefined symbol: dbm_firstkey
Should I
I can't really believe that I had to patch this. Maybe I'm just the
first to try... Frankly, I can't believe that the glibc folk did this...
*** mod_ssl.h.orig Mon Sep 27 19:49:46 1999
--- mod_ssl.h Mon Sep 27 19:49:56 1999
***
*** 264,269
--- 264,280
#include
Full_Name: Dom Gallagher
Version: 2.4.2
OS: Linux Slackware 3.x + 2.2.9
Submission from: amethyst.stayfree.co.uk (195.182.191.145)
[notice] child pid 855 exit signal Segmentation fault (11)
Getting a lot of instances of this message, which causes failed connects on the
clients - eventually the
Images on the sercure page need to reference with image URLs with "https"
instead of "http". Example: On the secure page https://www.myurl.com, the
image title image would be img src="https://www.myurl.com/title_image.gif"
hope this helps
K. Dunn
Hi,
I tried what Jeff suggested below but
Yes, here is the cert I'm having the problem with. I've had
Thawte triple check it, and they have found no problems. This
is a cert for a client of mine, of course.
-BEGIN CERTIFICATE-
MIICsDCCAhmgAwIBAgIDAIPNMA0GCSqGSIb3DQEBBAUAMIHEMQswCQYDVQQGEwJa
Hi,
My Apache 1.3.9 server sends out images encrypted.
How can I send images not encrypted and save some resources.
mod_proxy plus mod_rewrite is your friend.
Create a fake URL for the graphics, say https://your.com/redirect_me/my.gif.
RewriteEngine on
RewriteRule
On Tue, Sep 28, 1999, [EMAIL PROTECTED] wrote:
Full_Name:
Version: 2.4.4
OS: Slackware-current
Submission from: dns0.prestoncoll.ac.uk (194.238.8.2)
hmm, very related to bug 291!
when using the "The flexible APACI-only way", everything works fine until here:
=== src/modules/ssl
On Tue, Sep 28, 1999, Magnus Stenman wrote:
2.4.3 compiled OK on my redhat 5.2 box, but 2.4.4 barfs:
gcc -c -I../../../../mm-1.0.11 -I../../os/unix -I../../include -O2 -m486
-fno-strength-reduce
-DLINUX=2 -DMOD_SSL=204104 -DEAPI -DEAPI_MM -DUSE_EXPAT -I../../lib/expat-lite
`../../apaci`
On Tue, Sep 28, 1999, [EMAIL PROTECTED] wrote:
Full_Name: Dom Gallagher
Version: 2.4.2
OS: Linux Slackware 3.x + 2.2.9
Submission from: amethyst.stayfree.co.uk (195.182.191.145)
[notice] child pid 855 exit signal Segmentation fault (11)
Getting a lot of instances of this message, which
On Tue, Sep 28, 1999, WSO Support wrote:
Yes, here is the cert I'm having the problem with. I've had
Thawte triple check it, and they have found no problems. This
is a cert for a client of mine, of course.
-BEGIN CERTIFICATE-
On Tue, Sep 28, 1999, Ralf S. Engelschall wrote:
On Tue, Sep 28, 1999, Magnus Stenman wrote:
2.4.3 compiled OK on my redhat 5.2 box, but 2.4.4 barfs:
gcc -c -I../../../../mm-1.0.11 -I../../os/unix -I../../include -O2 -m486
-fno-strength-reduce
-DLINUX=2 -DMOD_SSL=204104 -DEAPI
Ok, as we recognized the nasty way, older Linux boxes (= glibc 2.1) have
broken semctl(2) prototypes which still cause compile problems for mod_ssl
2.4.4. I've now fixed this for 2.4.5 with the appended patch, but I don't want
to kick out 2.4.5 immediately just because some older Linux platforms
On Tue, Sep 28, 1999, Igor S. Livshits wrote:
Cristi's patch and the 2.4.4 release solved my compile problem.
However, when I build using APXS, I still cannot properly link at
run-time:
Cannot load /usr/local/apache/libexec/libssl.so into server:
/usr/local/apache/libexec/libssl.so:
On Mon, Sep 27, 1999, Igor S. Livshits wrote:
I don't think I have ever successfully compiled mod_ssl using
Apache's apxs; however, it compiles and works fine as a shared
library otherwise. This is the compile error I get for version 2.4.3
(2.4.2 running currently):
gcc -c
On Tue, Sep 28, 1999 at 09:36:01PM +0200, Ralf S. Engelschall wrote:
incompatible type for the forth argument. Hmmm... seems like I've to try
it now myself on a Linux box to make it running. As a workaround, just
remove line 260 in mod_ssl.h.
Looks like 2.4.5? :)
Does the current (or will
As always, shit happens twice. Hell, why are Linux boxes such nasty? I still
do not understand why a semctl(x,x,x,...) function can complain about an
incompatible type for the forth argument. Hmmm... seems like I've to try
it now myself on a Linux box to make it running. As a workaround,
At 10:28 PM +0200 on 9/28/99, Ralf S. Engelschall wrote:
On Tue, Sep 28, 1999, Igor S. Livshits wrote:
Cristi's patch and the 2.4.4 release solved my compile problem.
However, when I build using APXS, I still cannot properly link at
run-time:
Cannot load
On Tue, 28 Sep 1999 [EMAIL PROTECTED] wrote:
[notice] child pid 855 exit signal Segmentation fault (11)
Getting a lot of instances of this message, which causes failed connects on the
clients - eventually the SSL part of apache seems to get bored, and stops
listening to ANY requests.
On Tue, 28 Sep 1999, Ralf S. Engelschall wrote:
On Tue, Sep 28, 1999, Ralf S. Engelschall wrote:
but RedHat 5.2 defined it incorrectly as:
extern int semctl __P ((int __semid, int __semnum, int __cmd,
union semun __arg));
That's unbelievable. Every time mod_ssl
"Ralf" == Ralf S Engelschall [EMAIL PROTECTED] writes:
Ralf Ok, as we recognized the nasty way, older Linux boxes (= glibc
Ralf 2.1) have broken semctl(2) prototypes which still cause compile
Ralf problems for mod_ssl 2.4.4. I've now fixed this for 2.4.5 with the
Uh, "older"?
Hi,
Platform: hpux-11, Apache-1.3.6, OpenSSL-0.9.3a, modssl-2.3.11
I'm trying to use Netscape CMS (cert management system) to generate some
user certs for SSL authentication. I've updated ca-bundled.crt with my CA
detailes. My CA key is 2048. My apache works fine in SSL mode if client cert
is
On Tue, 28 Sep 1999 [EMAIL PROTECTED] wrote:
Full_Name: Dom Gallagher
Version: 2.4.2
OS: Linux Slackware 3.x + 2.2.9
Submission from: amethyst.stayfree.co.uk (195.182.191.145)
[notice] child pid 855 exit signal Segmentation fault (11)
Getting a lot of instances of this message, which
On Tue, 28 Sep 1999 [EMAIL PROTECTED] wrote:
Full_Name: Dom Gallagher
Version: 2.4.2
OS: Linux Slackware 3.x + 2.2.9
Submission from: amethyst.stayfree.co.uk (195.182.191.145)
[notice] child pid 855 exit signal Segmentation fault (11)
Getting a lot of instances of this message, which
34 matches
Mail list logo
