Re: SSLRequireSSL

2001-03-09 Thread Owen Boyle
"Brett W. McCoy" wrote: Maybe I am missing something about the use of SSLRequireSSL, but I am trying to control access to a directory so that only connections using SSL to that directory can be made. But no matter what directory I use that directive in, non-SSL connections can still

Re: SSLRequireSSL

2001-03-09 Thread Brett W . McCoy
On 2001.03.09 03:28 Owen Boyle wrote: There are many ways to control access and the override rules can get a bit complicated. I suspect your SSLRequireSSL is being overridden by a later directive in the non-SSL Vhosts or in a .htaccess file... Nope, that wasn't the case at all. The sanest

RE: apache 1.319 + modssl 2.8.1 on windows

2001-03-09 Thread Daniel S. Reichenbach
Oops! I had the name for file (2) wrong, I think this is correct: The Apache_1.3.19 and modssl_2.8.1 source file from March 3 needs the following from the CVSWeb: (1) [modssl] / mod_ssl / pkg.mod_ssl / configure.bat (2) [modssl] / mod_ssl / pkg.mod_ssl / pkg.sslmod / Makefile.win32 I'm

RE: Apache 1.3.17 - mod_ssl.2.8.0 - openssl.0.9.6 Reverse Proxy SSL

2001-03-09 Thread De Taeye, Herman
Hi, I am trying to setup this with 2 apache systems, but when using SSL connections, I always get a handshake problem, between the proxy and the application server. The client uses Unauthenticated SSL to the proxy. Between the proxy and the applications server, SSL is used where the application

RE: reverse proxy

2001-03-09 Thread John . Airey
So... what are you trying to say? This slightly improved security is not worth the setup hassle? So why do YOU run it this way? ;) First of all, it isn't necessary to use the SSL_EXPERIMENTAL code to get this to work. Secondly, we do things this way because of our network topology. We

RE: apache 1.319 + modssl 2.8.1 on windows

2001-03-09 Thread Deocs Postmaster
At 06:18 AM 3/9/01 , you wrote: Oops! I had the name for file (2) wrong, I think this is correct: The Apache_1.3.19 and modssl_2.8.1 source file from March 3 needs the following from the CVSWeb: (1) [modssl] / mod_ssl / pkg.mod_ssl / configure.bat (2) [modssl] / mod_ssl / pkg.mod_ssl

RE: apache 1.319 + modssl 2.8.1 on windows

2001-03-09 Thread Daniel S. Reichenbach
How far did you make it through INSTALL.Win32 before it failed? Up to the build process, it crashed on mod_ssl.c. I downloaded the 2.8.1 distribution and fetched the files you listed from CVSweb, replaced them and started the build process. Perhaps you can send me the files you used to

RE: apache 1.319 + modssl 2.8.1 on windows

2001-03-09 Thread Deocs Postmaster
At 07:33 AM 3/9/01 , you wrote: How far did you make it through INSTALL.Win32 before it failed? Up to the build process, it crashed on mod_ssl.c. I downloaded the 2.8.1 distribution and fetched the files you listed from CVSweb, replaced them and started the build process. Perhaps you can send

RE: apache 1.319 + modssl 2.8.1 on windows

2001-03-09 Thread Daniel S. Reichenbach
It could be having trouble finding the openssl include files. In addition to the two files listed earlier, I interpreted: Install OpenSSL into $INSTALLTOP. You have do this by hand: ... $ copy /b inc32\* p:\openssl\include\openssl ... YES, it was this one... SSL_INC

RE: SSLRequireSSL

2001-03-09 Thread Chong, Arthur
Pardon my *stupidity* but when you say _default_:443 you really mean whatever the IP addresss is or virtual domain name lime "www.mydomain.com" - right? VirtualHost _default_:443 ... Directory /home/www/secure SSLRequireSSL ... /Directory /VirtualHost -Original

RE: SSLRequireSSL

2001-03-09 Thread Brett W. McCoy
On Fri, 9 Mar 2001, Chong, Arthur wrote: Pardon my *stupidity* but when you say _default_:443 you really mean whatever the IP addresss is or virtual domain name lime "www.mydomain.com" - right? VirtualHost _default_:443 ... Directory /home/www/secure SSLRequireSSL ...

Re: SSLRequireSSL

2001-03-09 Thread Owen Boyle
"Chong, Arthur" wrote: Pardon my *stupidity* but when you say _default_:443 you really mean whatever the IP addresss is or virtual domain name lime "www.mydomain.com" - right? Yes. It's just to make the instructions generic and not specific to any particular installation. Rgds, Owen

RE: SSLRequireSSL

2001-03-09 Thread Chong, Arthur
Thanks, that worked! Brett, In the scenario you implemented with "Tomcat and JSPs and servlets and all..." do you actually support different virtual hosts with specific directories that are secure using the "redirects from non-secure area to secure area"...? How would you handle different

it runs but that's about it

2001-03-09 Thread Justin Naik
can anyone please tell me how to search for errors in my SSL installation Redhat linux 6.2 apache 1.3.12 i've done all the things i'm told to with Open SSL an MOD SSL. The apache server starts up ok in normal form and even starts up with -startssl parameter. But I go to https://myaddress.com

RE: it runs but that's about it

2001-03-09 Thread Chong, Arthur
Here is an example SSL section. It lists the Errorlog - go there to see where the error is...so if your ServerRoot is /www, the logs are at /www/logs IfDefine SSL VirtualHost _default_:443 #DocumentRoot /home/secure #ServerName mooey.ee.com #ServerAlias mooey.ee.com ErrorLog

Re: it runs but that's about it

2001-03-09 Thread Paul
--- Justin Naik [EMAIL PROTECTED] wrote: . . . The apache server starts up ok in normal form and even starts up with -startssl parameter. But I go to https://myaddress.com and I get a doesn't exist error HELP! - where do I start to look for errors - I have no idea! What sort of "doesn't

newbie question about client certificate authentication errors

2001-03-09 Thread william f guyton jr
ok, running mod_ssl 2.8.1 and apache 1.3.19, made my own CA for the server and can connect via 443 with no problems. wanting to do plain certificate authentication via a client certificate, so in did: openssl pkcs12 -export -in /usr/local/apache/conf/ssl.crt/ca.crt -inkey

RE: SSLRequireSSL

2001-03-09 Thread Brett W. McCoy
On Fri, 9 Mar 2001, Chong, Arthur wrote: In the scenario you implemented with "Tomcat and JSPs and servlets and all..." do you actually support different virtual hosts with specific directories that are secure using the "redirects from non-secure area to secure area"...? How would you