270 reputation
17
bio website crash.net.nz
location London, United Kingdom
age 36
visits member for 1 year, 5 months
seen Dec 9 '13 at 9:46
OOk?

Jun
10
awarded  Yearling
Jul
23
comment Require SSL client certificates from all remote (not local) clients?
Sorry, all I meant was that assigning two names to your external IP, and then using the name to determine whether to use client cert authentication would be a bad idea. By using localhost or another internal-only IP for local access, external users won't be able to connect to the unauthenticated virtual host at all.
Jul
22
comment Require SSL client certificates from all remote (not local) clients?
Using two DNS names for the same IP and then using the name to select a virtual host would not be a good idea. You might be able to get it working using SNI, but it would be easily circumvented by an external user who knew the 'local' name.
Jul
22
comment Require SSL client certificates from all remote (not local) clients?
Sure, it doesn't need to be localhost. Add a second internal-only IP address to the box and add your local DNS entry for that new IP. Ensure the second IP is not accessible to external clients though.
Jul
16
answered Require SSL client certificates from all remote (not local) clients?
Jun
21
awarded  Editor
Jun
21
revised What is wrong with this apache URL rewriting rule?
Expanded on answer.
Jun
21
answered What is wrong with this apache URL rewriting rule?
Jun
21
answered RFC 2616 with Apache 2.4
Jun
20
comment Apache Proxy - SSL Authentication failure on back end of proxy (Client side)
Does the openssl command prompt you for a password? If so, you are using an encrypted private key. This is not supported by SSLProxyMachineCertificateFile. A quick Google search will tell you how to remove the passphrase if you wish to do so.
Jun
19
answered Apache Proxy - SSL Authentication failure on back end of proxy (Client side)
Jun
17
awarded  Organizer
Jun
17
revised If I create a virtualhost for a new domain, do I have to create a second virtualhost to maintain the preexisting, straight through access?
Removed centos tag - Question is not OS specific.
Jun
17
suggested suggested edit on If I create a virtualhost for a new domain, do I have to create a second virtualhost to maintain the preexisting, straight through access?
Jun
17
comment If I create a virtualhost for a new domain, do I have to create a second virtualhost to maintain the preexisting, straight through access?
Yes it is - Apache doesn't care or know if the configured IPs are public or private. If the virtual host and main server are going to listen on the same IP and port, you will need a default virtual host.
Jun
17
answered If I create a virtualhost for a new domain, do I have to create a second virtualhost to maintain the preexisting, straight through access?
Jun
14
awarded  Supporter
Jun
14
answered Passing Client IP across Multiple Proxies
Jun
11
awarded  Teacher
Jun
11
answered Are Apache logs needed when Piwik is being used