AFAIK you can use the same server.key to sign multiple certificates.

      You're correct that each domain needs it's own certificate but I don't
      think the same is true for the private keys.

      HTH,

      Simon Wilcox.






Please respond to [EMAIL PROTECTED]

             (Embedded image moved to file: pic16165.pcx) (Embedded image moved
to file: pic22949.pcx)

        From           Giuliano Cocchi <[EMAIL PROTECTED]>
                                    Date   7 September 2000
             (Embedded image moved to file: pic02618.pcx)   (Embedded image
moved to file: pic27884.pcx)
                                                                           
                [EMAIL PROTECTED]                    Time      15:32 
       To                                                                  
                                                                           

             (Embedded image moved to file: pic18806.pcx)   (Embedded image
moved to file: pic16421.pcx)

              Copy to           (bcc: Simon Wilcox/BASE/WilliamsLea)
             (Embedded image moved to file: pic10399.pcx)

                           Fax to
             (Embedded image moved to file: pic30029.pcx)

                  Subject        Re: server.key
             (Embedded image moved to file: pic31203.pcx)





Yes you do.
One certificate for each domain.

On Thu, 07 Sep 2000, you wrote:
> >%_Hi,
>
>     Do I need to generate different server key for different domain name ??
>
> Thank you so much for your help
>
> mark
>

----------------------------------------
Content-Type: text/html; name="unnamed"
Content-Transfer-Encoding: quoted-printable
Content-Description:
----------------------------------------
______________________________________________________________________
Apache Interface to OpenSSL (mod_ssl)                   www.modssl.org
User Support Mailing List                      [EMAIL PROTECTED]
Automated List Manager                            [EMAIL PROTECTED]











______________________________________________________________________


   This email contains proprietary information some or all of which may be
   legally privileged.  It is for the intended recipient only. If an addressing
   or transmission error has misdirected this email, please notify the author by
   replying to this email. If you are not the intended recipient you must not
   use, disclose, distribute, copy, print, or reply on this email.

pic16165.pcx

pic22949.pcx

pic02618.pcx

pic27884.pcx

pic18806.pcx

pic16421.pcx

pic10399.pcx

pic30029.pcx

pic31203.pcx

Reply via email to