hUnTeR schrieb:
>
> Well i did do a ton of reading, and yes even tried the CA.pl(sh) script.
> What it turned out to be, just for anyone else that is curious, is that
> the Location (city) needed to be different between the CA and the server
> cert itself. Once i made that one and only change, it
I'm clearly a stupid fsck, but perhaps this tip will help other stupid
fscks out there running Apache and modssl on Linux.
I was having trouble with long (really long, sometimes) connect times
on SSL connections. Sometimes things would go through immediately, or
within a second or two, but often
Hi all,
I'm on RH 6.1, Apache 1.3.9, modssl 2.4.8-1.3.9, and openssl 0.9.4. When
I attempted to establish a secure connection, my Netscape browser
complained about an incorrect "Message Authentication Code." The end of
ssl_engine_log looks like this:
[10/Nov/1999 20:47:25 25706] [info] Conne
>
>
> I have been requested by one of my clients to support FrontPage extensions
> on my MkLinux box currently running Apache-1.3.6 and mod_ssl 2.3.4
>
> The FrontPage extensions patches are for 1.3.6 Apache only. Current
> mod_ssl 2.4.8 is for apache_1.3.9. What should I do: stay at current
>
Not necessarily. You can configure FP so that it will allow only a
group of IP addresses in, for instance. But yes, installing the FP
extensions should not be undertaken lightly, and only after reading (and
rereading, unfortunately) ALL the FP docs about ownership, permissions,
passwords, etc.
yer dilema is worse then ya think, add frontpage extensions only if this
server is on the DMZ and you are willing to sacrifice it and reinstall
from backups often.
Thanks,
Ron DuFresne
On Wed, 10 Nov 1999, Mark Jaffe wrote:
>
> I have been requested by one of my clients to support FrontPage
I have been requested by one of my clients to support FrontPage extensions
on my MkLinux box currently running Apache-1.3.6 and mod_ssl 2.3.4
The FrontPage extensions patches are for 1.3.6 Apache only. Current
mod_ssl 2.4.8 is for apache_1.3.9. What should I do: stay at current
apache and mod_s
"Ralf S. Engelschall" wrote:
> In 90% of all cases where one receives this error this was caused by a cached
> old certificate/key information in the browser. And one can get rid of the
> error by just removing all cached cert/keys in the browsers security dialogs.
> Typical error is that the bro
On Tue, Nov 09, 1999, Robert Flemming wrote:
> [...]
> routines:RSA_padding_check_PKCS1_type_2:block type is not 02
> [error] OpenSSL: error:04065072:rsa
> routines:RSA_EAY_PRIVATE_DECRYPT:padding check failed
> [error] OpenSSL: error:1408F071:SSL routines:SSL3_GET_RECORD:bad mac
> decode
>
> If
On Tue, Nov 09, 1999, [EMAIL PROTECTED] wrote:
> You have not mentioned where you put your private key by using the
> directive SSLCertificateKeyFile. Have you placed your keyfile to an
> appropriate place and pointed SSLCertificateKeyFile to this file.
>
> Note that mod_ssl does not complain ab
On Tue, Nov 09, 1999, Chris Ingrassia wrote:
> On Tue, 9 Nov 1999, R. DuFresne wrote:
> > you apaches is 6 revs old, I think yer open ssl is a rev or two old, I'm
> > betting yer suse linux is also old and lacking many significant updates
> > and fixes. I'd advise first off that you upgrade it a
11 matches
Mail list logo
