Skip to main content
deleted 2 characters in body
Source Link
schroeder
  • 132.1k
  • 55
  • 307
  • 348

My understanding is that for each SSL certificate, there is a private and public key, which that web browsers use to confirm that it is a valid certificate signed by a trusted certificate authorityCertificate Authority. Now how

How does the certificate authorityCertificate Authority decide which private key and public key will be used to encrypt each certificate for verification by the browser? Do they have different private/public keys for each certificate?

My understanding is that for each SSL certificate, there is a private and public key, which web browsers use to confirm that it is a valid certificate signed by a trusted certificate authority. Now how does the certificate authority decide which private key and public key will be used to encrypt each certificate for verification by the browser? Do they have different private/public keys for each certificate?

My understanding is that for each SSL certificate, there is a private and public key that web browsers use to confirm that it is a valid certificate signed by a trusted Certificate Authority.

How does the Certificate Authority decide which private key and public key will be used to encrypt each certificate for verification by the browser? Do they have different private/public keys for each certificate?

Post Closed as "Duplicate" by Steffen Ullrich tls
Source Link

How do certificate authorities choose which private/public keys to use to encrypt each SSL certificate so a browser can know that they're legit?

My understanding is that for each SSL certificate, there is a private and public key, which web browsers use to confirm that it is a valid certificate signed by a trusted certificate authority. Now how does the certificate authority decide which private key and public key will be used to encrypt each certificate for verification by the browser? Do they have different private/public keys for each certificate?