Synchronized issuance of public X.509 digital certificates

1. A method, comprising:

generating, using a processor of a web server, a short-term private key, the short-term private key expiring after a period less than a year in length;

generating a request for a public key certificate;

sending the request for the public key certificate to a trusted third party over a public network, the trusted third party comprising a Certificate Authority (CA);

receiving, over the public network, the public key certificate from the CA, the public key certificate signed by the CA;

pairing the short-term private key with the public key certificate received from the CA; and

transmitting the public key certificate received from the CA to a plurality of distribution addresses, wherein the plurality of distribution addresses belong to a plurality of third parties.

2. The method of claim 1 , further comprising signing the request for the public key certificate,

wherein the signature of the request for the public key certificate is verified by the CA before the CA signs the public key certificate.

3. The method of claim 1 , wherein the public key certificate received from the CA is transmitted to the plurality of distribution addresses contemporaneously with receiving the public key certificate from the CA.

4. The method of claim 1 , further comprising generating, using the processor, a list of the plurality of distribution addresses.

5. The method of claim 1 , further comprising receiving a list of the plurality of distribution addresses from a certificate user.

6. The method of claim 5 , wherein the list of the plurality of distribution addresses is received via a configuration file.

7. The method of claim 1 , further comprising:

generating, using the processor, a second private key-public key pair, the second private key-public key pair comprising a second private key and a second public key;

generating a request for a second public key certificate, the request for the second public key certificate comprising the second public key;

sending the request for the second public key certificate to the CA; and

receiving an indication that the CA will not send the second public key certificate.

8. The method of claim 7 , wherein the CA will not send the second public key certificate because the second public key is invalid, and

wherein the method further comprises discarding the second private key-public key pair after receiving the indication that the CA will not send the second public key certificate.

9. The method of claim 8 , wherein the public key being invalid comprises the second public key having expired.

10. A computer configured to access a storage device, the computer comprising:

a processor; and

a non-transitory, computer-readable storage medium storing computer-readable instructions that when executed by the processor cause the computer to perform:

generating, at a web server, using the processor, a short-term private key, the short-term private key expiring after a period less than a year in length;

generating a request for a public key certificate;

sending the request for the public key certificate from the web server to a trusted third party over a public network, the trusted third party comprising a Certificate Authority (CA);

in response to receiving the public key certificate from the CA over the public network, the public key certificate signed by the CA, pairing the short-term private key with the public key certificate received from the CA; and

contemporaneously with receiving the public key certificate from the CA, transmitting the public key certificate received from the CA to a plurality of distribution addresses, wherein the plurality of distribution addresses belong to a plurality of third parties.

11. The computer of claim 10 , wherein the computer-readable instructions further cause the computer to perform signing the request for the public key certificate,

wherein the signature of the request for the public key certificate is verified by the CA before the CA signs the public key certificate.

12. The computer of claim 10 , wherein the computer-readable instructions further cause the computer to perform generating, using the processor, a list of the plurality of distribution addresses.

13. The computer of claim 10 , wherein the computer-readable instructions further cause the computer to perform receiving a list of the plurality of distribution addresses from a certificate user.

14. The computer of claim 13 , wherein the list of the plurality of distribution addresses is received via a configuration file.

15. The computer of claim 10 , wherein the computer-readable instructions further cause the computer to perform:

generating, using the processor, a second private key-public key pair, the second private key-public key pair comprising a second private key and a second public key;

generating a request for a second public key certificate, the request for the second public key certificate comprising the second public key;

sending the request for the second public key certificate to the CA; and

receiving an indication that the CA will not send the second public key certificate.

16. The computer of claim 15 , wherein the CA will not send the second public key certificate because the second public key is invalid, and

wherein the computer-readable instructions further cause the computer to perform discarding the second private key-public key pair after receiving the indication that the CA will not send the second public key certificate.

17. The computer of claim 16 , wherein the second public key being invalid comprises the second public key having expired.

18. A non-transitory computer-readable storage medium storing instructions that are executable to cause a system to perform operations comprising:

retrieving a list of a plurality of distribution addresses, wherein the plurality of distribution addresses belong to a plurality of third parties;

generating, at a web server, using a processor, a short-term private key, the short-term private key expiring after a period less than a year in length;

generating a request for a public key certificate;

sending the request for the public key certificate from the web server to a trusted third party over a public network, the trusted third party comprising a Certificate Authority (CA);

in response to receiving the public key certificate from the CA over the public network, the public key certificate signed by the CA, pairing the short-term private key with the public key certificate received from the CA; and

contemporaneously with receiving the public key certificate from the CA, transmitting the public key certificate received from the CA to a plurality of distribution addresses.