Security FAQ
From Resin 3.0
(New page: === Can I use different SSL certificates for each virtual host? === <p>''We have two domains on one server. Is there an example config file showing how to have multiple ssl certificates,...) |
|||
| (3 intermediate revisions by one user not shown) | |||
| Line 1: | Line 1: | ||
=== Can I use different SSL certificates for each virtual host? === | === Can I use different SSL certificates for each virtual host? === | ||
| − | <p>''We have two domains on one server. Is there an example config file showing | + | <p>''We have two domains on one server. Is there an example config file showing how to have multiple ssl certificates, one for each virtual host?''</p> |
| − | how to have multiple ssl certificates, one for each virtual host? | + | |
| − | ''</p> | + | |
<p>This is not possible if you are using Resin's virtual hosting capability to | <p>This is not possible if you are using Resin's virtual hosting capability to | ||
| Line 10: | Line 8: | ||
<p>The SSL connection (and certificate) are handled before the HTTP request is | <p>The SSL connection (and certificate) are handled before the HTTP request is | ||
sent. Unless the domain name is mapped to a unique ip address, the server | sent. Unless the domain name is mapped to a unique ip address, the server | ||
| − | + | cannot know which domain name the user is using until after SSL is set up. | |
There is no way for Resin to determine which domain name the user has specified | There is no way for Resin to determine which domain name the user has specified | ||
| − | in the | + | in the request until after the SSL decryption has occurred.</p> |
| − | <p>It is possible | + | <p>It is possible if you have separate IP addresses for the hosts. You need |
| − | + | unique http port listeners that only bind on that ip | |
| − | address. Each of these http | + | address. Each of these http ports can have it's own ssl |
configurations.</p> | configurations.</p> | ||
| + | |||
| + | <code><pre> | ||
| + | <resin xmlns="http://caucho.com/ns/resin"> | ||
| + | <cluster id=""> | ||
| + | |||
| + | <server id=""> | ||
| + | <http address="*" port="80"/> | ||
| + | |||
| + | <http address="199.199.0.10" port="443" virtual-host="gryffindor.com"> | ||
| + | <openssl> | ||
| + | <certificate-file>keys/gryffindor.crt</certificate-file> | ||
| + | <certificate-key-file>keys/gryffindor.key</certificate-key-file> | ||
| + | <password>test123</password> | ||
| + | </openssl> | ||
| + | </http> | ||
| + | |||
| + | <http address="199.199.0.11" port="443" virtual-host="slytherin.com"> | ||
| + | <openssl> | ||
| + | <certificate-file>keys/slytherin.crt</certificate-file> | ||
| + | <certificate-key-file>keys/slytherin.key</certificate-key-file> | ||
| + | <password>test123</password> | ||
| + | </openssl> | ||
| + | </http> | ||
| + | |||
| + | ... | ||
| + | </server> | ||
| + | |||
| + | <host id="gryffindor.com"> | ||
| + | <host-alias>www.gryffindor.com</host-alias> | ||
| + | |||
| + | ... | ||
| + | |||
| + | </host> | ||
| + | |||
| + | <host id="slytherin.com"> | ||
| + | <host-alias>www.slytherin.com</host-alias> | ||
| + | |||
| + | ... | ||
| + | </host> | ||
| + | |||
| + | ... | ||
| + | </cluster> | ||
| + | </resin> | ||
| + | </pre></code> | ||
=== Why does Resin say I need OPENSSL_THREADS when I try to use OpenSSL? === | === Why does Resin say I need OPENSSL_THREADS when I try to use OpenSSL? === | ||
<p>''Resin dies with an error on startup "Resin requires a threaded version of OpenSSL. OpenSSL must be compiled with OPENSSL_THREADS for Resin to use it."''</p> | <p>''Resin dies with an error on startup "Resin requires a threaded version of OpenSSL. OpenSSL must be compiled with OPENSSL_THREADS for Resin to use it."''</p> | ||
| − | |||
Resin requires a threaded version of the OpenSSL libraries. Usually a threaded | Resin requires a threaded version of the OpenSSL libraries. Usually a threaded | ||
version is the default for OpenSSL, however on some systems it is necessary to | version is the default for OpenSSL, however on some systems it is necessary to | ||
| − | explicitly request a thread version. | + | explicitly request a thread version. |
<p> | <p> | ||
| Line 56: | Line 97: | ||
<-Finished | <-Finished | ||
</pre></code> | </pre></code> | ||
| + | |||
| + | === How do I handle port 80 and root issues on Linux? === | ||
| + | |||
| + | Use Resin 3.1 Professional with the <user-name> tag. The Resin [watchdog] will start as root and bind to port 80 as root. Before the watchdog launches the Resin instance, it will change to the <user-name>. | ||
| + | |||
| + | === Where can I learn more about SSL? === | ||
| + | |||
| + | * [http://httpd.apache.org/docs-2.0/ssl/ssl_intro.html Apache documentation] | ||
| + | |||
| + | === Converting a JSSE Keystore to OpenSSL === | ||
| + | |||
| + | * [http://www.thauvin.net/blog/stories.jsp?id=42 Erik's Weblog - Converting a JSSE Keystore to OpenSSL] | ||
Latest revision as of 17:06, 1 April 2008
Can I use different SSL certificates for each virtual host?
We have two domains on one server. Is there an example config file showing how to have multiple ssl certificates, one for each virtual host?
This is not possible if you are using Resin's virtual hosting capability to serve to multiple domain names using a single IP address.
The SSL connection (and certificate) are handled before the HTTP request is sent. Unless the domain name is mapped to a unique ip address, the server cannot know which domain name the user is using until after SSL is set up. There is no way for Resin to determine which domain name the user has specified in the request until after the SSL decryption has occurred.
It is possible if you have separate IP addresses for the hosts. You need unique http port listeners that only bind on that ip address. Each of these http ports can have it's own ssl configurations.
<resin xmlns="http://caucho.com/ns/resin">
<cluster id="">
<server id="">
<http address="*" port="80"/>
<http address="199.199.0.10" port="443" virtual-host="gryffindor.com">
<openssl>
<certificate-file>keys/gryffindor.crt</certificate-file>
<certificate-key-file>keys/gryffindor.key</certificate-key-file>
<password>test123</password>
</openssl>
</http>
<http address="199.199.0.11" port="443" virtual-host="slytherin.com">
<openssl>
<certificate-file>keys/slytherin.crt</certificate-file>
<certificate-key-file>keys/slytherin.key</certificate-key-file>
<password>test123</password>
</openssl>
</http>
...
</server>
<host id="gryffindor.com">
<host-alias>www.gryffindor.com</host-alias>
...
</host>
<host id="slytherin.com">
<host-alias>www.slytherin.com</host-alias>
...
</host>
...
</cluster>
</resin>
Why does Resin say I need OPENSSL_THREADS when I try to use OpenSSL?
Resin dies with an error on startup "Resin requires a threaded version of OpenSSL. OpenSSL must be compiled with OPENSSL_THREADS for Resin to use it."
Resin requires a threaded version of the OpenSSL libraries. Usually a threaded version is the default for OpenSSL, however on some systems it is necessary to explicitly request a thread version.
To recompile the openssl libraries with threading enabled:
$ cd openssl-0.9.7c
$ ./config threads
$ make
$ make install
The INSTALL document from the OpenSSL package contains more
information on the threads option.
What is the sequence of handshakes for an SSL connection?
ClientHello->
<-ServerHello
<-CertificateChain
<-ServerHelloDone
ClientKeyExchange->
ChangeCipherSpec->
Finished->
<-ChangeCipherSpec
<-Finished
How do I handle port 80 and root issues on Linux?
Use Resin 3.1 Professional with the <user-name> tag. The Resin [watchdog] will start as root and bind to port 80 as root. Before the watchdog launches the Resin instance, it will change to the <user-name>.
