This is the process that I have successfully used to generate CSR's to obtain a certificate from Verisign: NB! This was for a Solaris installation using the openssl utilities that you must have had access to in order to compile mod_ssl in the first place. It is assumed that openssl is in your search path. 1. Create an RSA private key: openssl genrsa -des3 -out server.key 1024 -rand file1:file2:file3:filen * where file1 to filen are any number of files used to generate a seed for rand. I tend to use all files in /var/adm. ** you will also be asked to provide a password 2. To look at the resultant private key: openssl rsa -noout -text -in server.key 3. To generate a CSR: openssl req -new -key server.key -out server.csr * Note the common name is your WEB SITE name. 4. To look at the resultant CSR: openssl req -noout -text -in server.csr 5. Send the server.csr to Verisign to produce a server.crt file. 6. To look at the resultant server.csr file: openssl x509 -noout -text -in server.crt I must have picked this stuff up directly from the mod_ssl website at some time. So it is all documented. regards mark =============== Scott wrote: > Speaking of certificates, Apache certificate generation provides a default > issuer of Snake Oil. If the company I work for plans to deploy its own web > servers and be the issuer via Verisign, what do I do about the Snake Oil > piece? Make certificate View=1 shows Snake Oil as the issuer, but my company as > the Subject. What do I do, and what do I send to Verisign for a formal > "real" key/certificate pair? > > Thanks in advance. > > Scott > > ______________________________________________________________________ > Apache Interface to OpenSSL (mod_ssl) www.modssl.org > User Support Mailing List [EMAIL PROTECTED] > Automated List Manager [EMAIL PROTECTED] ______________________________________________________________________ Apache Interface to OpenSSL (mod_ssl) www.modssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
