Score:0

How networking secures the connection between Certificate Authority and Client?

us flag

I know HTTPS is based on the Certificate Authority (CA). If a client tries to send a request to a server (Assuming there is a Certificate), is it possible that a middleman can take the certificate from client and get the public key from the CA? At the same time, the middleman gives a fake Certificate to the Client and when the client sends a Certificate to CA, the middleman again intercepts it and give him fake public key.

I hope my question is clear enough. Thanks.

in flag
Public keys and certicates are always public, while the private key is keept private and never sent.
Score:4
cn flag

Under normal circumstances the client doesn't connect to the CA when making a HTTPS (or any other TLS) connection, they have a local copy of all the CA certificates they trust to issue server certificates.

So the client connects to the server, which sends the client a copy of it's server certificate, this contains a hash signed by the CA's private key, which is checked with the client's local copy of the CA's public key.

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.