Certificates are issued by maintaining chain of trust. Your certificate can be signed by either root ca or intermediate ca. Both of them use their private key to sign your certificate. When intermediate ca signs your certificate then it is doing that on behalf of root ca in order to off-load root ca's tasks.
As intermediate ca signs your web server certificate, like the same way root ca signs intermediate ca's certificate so that web browser can verify that by using root ca's public key.
Once the web server certificate is signed then a certificate bundle is created in which root ca's certificate, intermediate ca's certificate and web server's certificate are send to the organization owner who owns the web server.
Note: OS, browsers already contains the root ca or intermediate ca's public key or certificate.
Sometimes the certificate bundle is send by the web server so that browser easily verify intermediate ca and root ca.
Web browser checks web server's certificate by extracting the public key of intermediate ca from the certificate. As web server certificate is signed by intermediate ca so web server's certificate contains intermediate ca's public key. Once it is assured that web server certificate is valid then it is go for checking intermediate ca's certificate is ok or not by extracting the public key of root ca. As root ca signed intermediate ca's certificate, so it shall also found ok. Here used asymmetric algorithm.
After that secure communication starts by generating secret, master secret and finally session keys. Here used symmetric algorithm for faster communication.
Avi
Comments
Post a Comment