Multiple ssl certs for the same IP?

Igor Sysoev is at
Mon May 5 09:19:27 MSD 2008

On Sun, May 04, 2008 at 06:26:14PM -0700, Rt Ibmer wrote:

> On a related note, I'm going to create a self-signed key so I can test https support with nginx and my deployment.  I read somewhere that care should be taken when deciding to assign a passphrase, because some applications may require you to enter the passphrase upon initialization.  Would that be the case with nginx?

With nginx you have two choices:
1) do not use passphrase at all,
2) enter it manually upon initialization.
nginx does not support automated procedure to enter passphrase upon
initialization, because from security point of view it's almost the same as
no passphrase at all.

> Also I'm a bit confused about the key gen process (having never done this before under Linux). I've found the various openssl commands to generate the key, but its unclear as to which openssl command generates the file that should be used for ssl_certificate, and which command should be used to generate the file for ssl_certificate_key.
> For instance I found this for generating a self-signed key for testing:
>    openssl req -new -x509 -nodes -out server.crt -keyout server.key
> That looks easy enough.  The server.crt goes to the ssl_certificate and server.key goes to ssl_certificate_key.
> But it gets a bit confusing when I look 's instructions for creating keys to be signed by a real certificate authority. This is what I've pieced together:
>   openssl genrsa -out /whatever/ 1024
>   openssl req -new -key /whatever/ -out /whatever/
> So in that case I would use for the ssl_certificate, and I'd use the file I get back from the certificate authority as the value for ssl_certificate_key?  Do I have this right? Thanks!

No, you should use your in ssl_certificate_key.
Also you should send to authority and use the returned
signed certificate in ssl_certificate.

Igor Sysoev

More information about the nginx mailing list