Comment Certificate with airSlate SignNow

Collate certificate

what is going on guys my name is Hussein and in this video I'm gonna discuss certificate authorities it was a very popular topic that a lot of people asked me to do so I'm talking about it again in this channel in order to talk about anything we don't ask the what it is we don't ask what is a certificate authority we don't ask what is a certificate we ask why does it exist and that just immediately answers a lot of questions because why does this deck exist there is a reason there was a problem at one point and we ran into it and we needed a solution we invented certificate for that solution and then we ended invented something to manage the certificate and that's the certificate authority so let's jump into it class example I have a client you guys love this hand motions don't you and you have a server right have a client the server they want to establish or simplicity's use HTTP right I know TLS can be established on another protocol but simplicity rules this is a web server caddy right and it's running on port 443 and and and let's say this web server is mm I don't know supposed to be Google right and this is a client about to consume the Google home page what do we do first we establish a TCP connection assuming HTTP to HTTPS read is not correct but let's assume HTTP - I'm assuming TCP connection three word handshake all that jazz now I have a stateful TCP connection so before we send any data the get request to actually give me the information from Google we establish the the other ssangshik talked about TLS all the time check out these playlists really the TLS I'm gonna make a playlist just four TLS because I have a lot of videos on TLS all right so now we establish a TLS right why TLS well we need to encrypt we need nobody we don't want anybody in the middle to actually sniff our stuff right I don't want people to see what I'm searching for so now I'm gonna do TLS hello all that jazz let's agree on a key so we the same key encrypt and decrypt right so there's simple stuff now the client and the server agrees on the key and then now the client sends the first get request encrypts it first with this with the same key that day I agreed upon and then send it the information the server receives that encrypted request anybody in the middle cannot find out what the heck they have they are talking about because it's encrypted nobody has the kicks of those two Google server receives that encrypted decrypted read it process that request build an index.html ship it back no before we ship it encrypted the same key ship it back and the client does the same thing decrypted crosses...