Networking Lessons

A third party called CA — Certificate Authority takes responsibility of authenticating a certificate owned by web-server for giving trust to a client.

Thus, to begin the communication — a) one party sends public key + digital certificate. this dig cert is validated against the trusted CA.

b) second party validates the certificate against CA and uses public-key in the message to decrypt and use the message

========================================

Issued by CA, verifies the dig cert + public key of the web-server.

scenario:

step1: client wants to communicate with web-server (yahoo /google etc)

step2: WS sends public key + cert signed by CA to client

step3: client (browser installed with CA’s pub keys) validates the dig cert => so WS can be trusted (pub key belongs to the server truely)

step4: client sends its “symmetric key” by encrypting with pub-key sent by server

step5: web-server decrypts the symm key with its private key (corresponding to pub-key it shared in step2).

From here on communication will happen with symm-key (which is shared safely between ws, client for this session)

Ex:

Related posts:

Heather Heinrichs is a midwife working in remote Hay River in Canada’s Northwest Territories — a sub-arctic town of 3,500 nestled on the south bank of Great Slave Lake. Until five years ago, women…

We are really excited about having strengthened our team in Oslo with front-end developer Megan Pearson and copywriter Maren Granrud.

I was waiting in line to register a letter in the post office at 33rd Street and 8th Avenue in New York. I noticed that the clerk appeared to be bored with the job—weighing envelopes, handing out…