Hi,
I'm trying to use :
-Apache 1.3.12
-mod_ssl 2.6.2
-openssl 0.9.5 (0.9.4 too)
-mod_php 3.0.15
with :
-linux 2.2.14 (on Suse 6.2)
-gcc 2.95.2
on Intel Pentium 2 hardware.
All this compiled fine (with a spec file), and applictions seems to work
fine except with own
Hi,
I'm trying to use :
-Apache 1.3.12
-mod_ssl 2.6.2
-openssl 0.9.5 (0.9.4 too)
-mod_php 3.0.15
with :
-linux 2.2.14 (on Suse 6.2)
-gcc 2.95.2
on Intel Pentium 2 hardware.
All this compiled fine (with a spec file), and applictions seems to work
fine except with own
Alex,,
The trouble with using self signed certs is that you need to install the CA
cert in the browser to stop messages popping up when you connect to the site -
obviously no real problem as you will either be using them for testing or in a
closed environment (or limited number of
Assuming we are talking about Thawte's server test certificates, they are
only for use for one month. Using them helps you to understand how to
install a real certificate without running the risk of destroying it (a very
real risk with NT!)
They are not intended for production use. Thawte's own
On Thu, Mar 02, 2000, Karl Denninger wrote:
How do I restrict access on a mod_ssl server in certain directories to ONLY
SSL encrypted sessions?
For SSL only (any ciphers allowed) use SSLRequireSSL. If you need more
fine-grained control, use either a SSLCipherSuite which contains only
strong
I figured this one out; easy to do with an .htaccess file.
--
--
Karl Denninger ([EMAIL PROTECTED]) Web: http://childrens-justice.org
Isn't it time we started putting KIDS first? See the above URL for
a plan to do exactly that!
On Thu, Mar 02, 2000 at 04:07:56PM -0600, Karl Denninger wrote:
[EMAIL PROTECTED] wrote:
Alex,,
The trouble with using self signed certs is that you need to install the CA
cert in the browser to stop messages popping up when you connect to the site -
obviously no real problem as you will either be using them for testing or in a
closed environment
On Fri, Mar 03, 2000 at 09:31:58AM +, [EMAIL PROTECTED] wrote:
Alex,,
The trouble with using self signed certs is that you need to install the CA
cert in the browser to stop messages popping up when you connect to the site -
obviously no real problem as you will either be using them
Hello.
on "client auth failed / mod_ssl-2.6.2"
[EMAIL PROTECTED]
at Fri, 03 Mar 2000 01:43:16 +0900
I wrote:
Client authentication came to fail in following situation.
Client:
c1: MSIE 5.0 (5.00.2314.1003) / Windows NT 4.0 SP5
c2: MSIE 5.01 (5.00.2919.6307) / Windows NT 4.0 SP5
Hi,
I've been trying to recompile ModSSL rel. 2.6.2 with Apache 1.3.12 and
OpenSSL rel. 0.9.5. on a Sun UltraSPARC running Solaris 2.7.
Of course I had the same problem that many others had before me.
Once everything gets compiled I issue the following command:
make certificate
On Jul 23, 10:43am, Karl Denninger wrote:
}
} How do I restrict access on a mod_ssl server in certain directories to ONLY
} SSL encrypted sessions?
}
} The syntax suggested in the apache.conf.default file doesn't appear to work
} - I'm sure I'm doing something stupid, and would appreciate a
On Fri, Mar 03, 2000, [EMAIL PROTECTED] wrote:
[...]
Still I get the same error.
SSLRandomSeed is for the PRNG under _RUNTIME_. The "make certificate"
step does not read the Apache configuration file.
How can I use the SSLRandomSeed with a $HOME/.rnd file?
Just create a $HOME/.rnd with
Running RHL 6.1
I'm probably blind and missing the paragraph completely in the
documentation...
Is there a particular directory where one puts the MOD_SSL and OPEN_SSL
tars for decompressing and running 'makes'.
Thanks
JANLU (Just Another New Linux User)
Karl,
Everything you say is true, and if you install a the CA certificate into
the browser then you will have the secure connection that you want, however if
you don't have the CA cert in the browser then the server that you are talking
to may not be who you then they are, so what? - this
14 matches
Mail list logo
