19:57
@AjmalMoochingal it's no different than any other signing
the quick high level version is that public keys for known CAs are in a trusted list distributed with the browser and curated by the browser maker (or OS vendor).
someone getting a cert then provides their public key to the CA and verifies their identity. The CA then hashes the whole thing and encrypts the hash with their private key. If the cert can be hashed and validated to match the encrypted hash decrypted with the CA's public key on file, then the browser knows that the cert was actually approved by the CA and can trust the public key it provides