All about DevOps and Site Reliability Engineering Practices

Earlier in this post, we have talked about TLS Working model and configuring it for application in kubernetes . Basically any HTTPS server open for client connections, will present a server certificate to client to verify against its trusted certificate authorities and if success, it does basic TLS handshake. Its more of a validating whether sever domain is authentic, using server certificate. What if there is a security requirement where client needs a valid certificate before it access server content, this is where mutual authentication fits in. Its basically establishing secure encrypted communication between two parties and authenticity of each party will be verified at other party end with presented certificate against certificate authority. The following diagram demonstrates steps involved in mutual authentication 1. Client requests sever for its content 2. Server replies back by presenting its server certificate 3. Server's identity will be tested by client using...

TLS basic working model:  Secure communication between the two entities is paramount in today's digital world. TLS provides the secure end to end communication between two machines over a network. Classic example of TLS model is accessing www.google.com(server) via browser(client). Following basic steps are involved * Client makes a call, when URL was entered in browser * Server sends its certificate * Browser will check any Root CA present for server certificate, if its present it will validate via digital sign. If not it asks user to trust the certificate, happens when we use self signed certificates. *  Client sends its certificates, will be verified at server, its optional * Once verification is done, it starts exchanging encrypting messages, which will be only decrypted using certs and keys at their end. Generating TLS certs: There are many tools in market through which we can generate certs. Openssl is one of the widely used opensource tool, we will ...