I've generated a self certified SSL cert for testing a new web site. The time has come for the site to go live and I now want to purchase a cert from GeoTrust. Can I use the same CSR that I generated for the self cert, or do I need to create a new one?



As long as your using the same key, domain (aka common-name), contact details and validity period you should be able to use the same CSR.

Though to be honest generating a CSR is a pretty simple job, so if you need to amend the contact details (which a lot of SSL providers are strict on) it's not a big deal.

| improve this answer | |
  • 1
    I agree. Generating a CSR is such a trivial task I don't see why you'd even bother trying to reuse one. – joeqwerty Jul 1 '11 at 12:18
  • 5
    Once you have OpenSSL installed, you can generate a new CSR in about 30 seconds. And if you think it will take you much longer- then definitely do it because you need the practice!!!!! – Austin ''Danger'' Powers Mar 31 '13 at 2:17
  • 1
    Not applicable to the OP's case, but if you're looking to use certificate pinning, it's more practical to use the same CSR than to update your client side apps. – black May 22 '16 at 6:29
  • If the key, domain, and details are the same, the CSR will be identical. – graywh Jun 5 '19 at 15:31

For your example case, I don't think it's worth trying to reuse CSRs. However, for a large diverse team Apple iOS developers (like I have) there is a good reason to do this. We create (actually, ask Apple to create) all our signing certs and push certs off the same private key. That way we can all collaborate easily on our 85+ apps. For this reason, we keep a single CSR lying around and always use the same one for as long as the key is valid.

As far as I know, there is no reason to repeatedly generate CSRs from a single private key. I'd love to be corrected if I am wrong.

| improve this answer | |
  • 10
    It's been 4 years with no correction. I guess I'm not wrong. – Bruno Bronosky Apr 6 '17 at 17:40

The main benefit of having limited-duration certificates is to reduce the damage if your private key is leaked. Somebody possessing the private key can otherwise impersonate being you forever if you reuse the CSR, because re-using the CSR implies reuse of your private key as well.

Please don't do that, it's better to automate generation of both the private keys as well as the CSRs and find convenient ways to distribute the ever-changing private keys to application build servers and push servers. Most mere mortal developers would normally never need to do a release/distribution-build for the app store anyhow, so won't need the private keys.

| improve this answer | |
  • 1
    While it's true that "re-using the CSR implies reuse of your private key as well", it does not mean that "impersonate being you forever if you reuse the CSR". If you decide to use a key for N months, it's fine to use the same CSR for those N months. – Bruno Bronosky Apr 6 '17 at 17:45
  • 2
    Yes, you're right Bruno. I assumed the people reusing the CSR did so out of ignorance and thus continued that practise "forever", however there might of course be a few who are aware of the issues and do so based on careful planning for a limited time. – Stefan L Apr 7 '17 at 6:53

You can indeed in theory reuse the same CSR, as this is just a container for

  • your Public Key (only Numbers used for RSA encryption (specific maths) )
  • your "Subject" details (who you are, what domain, etc ...) Text used to Identify the owner of that Public Key

This is what a certificate (short for PublicKey Certificate) is about after all

But as noted in other answers, it is a good pratice to change private key regularly, so that implies new Certificate, and so new CSR to get it.

You can easily look at the contents of a CSR


$ openssl req -new -batch -subj "/CN=My Common Name/OU=My Org Unit/O=My Organisation" -sha256 -newkey rsa:2048 -keyout private.key -nodes -out request.csr
Generating a 2048 bit RSA private key
writing new private key to 'private.key'

$ ls
private.key  //  keep that private, the PublicKey side is easily be generated from this
request.csr // your PublicKey + Subject details


$ openssl req -in request.csr -text -noout
Certificate Request:
        Version: 1 (0x0)
        Subject: CN = My Common Name, OU = My Org Unit, O = My Organisation
        Subject Public Key Info:
            Public Key Algorithm: rsaEncryption
                RSA Public-Key: (2048 bit)
                Modulus:                    ///////// Matches the PrivateKey modulus
                Exponent: 65537 (0x10001)   ///////// Matches the PrivateKey publicExponent
    Signature Algorithm: sha256WithRSAEncryption

And PrivateKey

$ openssl rsa -in private.key -text -noout
// all the below are numbers that takes part in Mathematical encryption (search for RSA maths)
RSA Private-Key: (2048 bit, 2 primes)

// The Numbers that can be freely published
publicExponent: 65537 (0x10001)

// The Numbers that must be kept private !
| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.