3 - Cryptography Basics - Digital Certificate

Рет қаралды 20,501

CBTVid

Күн бұрын

In this video you'll learn about Digital Certificate and it's applications

Пікірлер: 24

@TheMato1112 Жыл бұрын

To be honest, this is the best video where I understood why it is happening. Thank you

@charmidoshi_1082 2 жыл бұрын

A crystal clear explaination .Thank you!!

@grjesus9979 3 жыл бұрын

Simply great! Thanks. I needed to see the bigger picture

@lordofperfection5528 9 ай бұрын

bro you explain it beautifully 😊😊👍👍

@citizenoftheworldsz9 2 жыл бұрын

amazingly explained, and brilliant example at the end, thank you!!!!!!!

@maidenfreek584 Жыл бұрын

Thank you! You deserve a lot more views.

@WeGrowAsOne Жыл бұрын

you mentioned one incorrect thing here, Bob can't decrypt Hash it's one way process instead he will calculate the hash on same information that he received from Alice using selected hashing algorithm and compare both the hash, correct me if I'm wrong here

@karrouchekarrouche1151 Жыл бұрын

He is right. The CA has encrypted the hash with its private key. What he meant is Bon is gonna decrypt the hash to compare it to the hash that he gonna independently calculate

@Reptil714 Жыл бұрын

Thanks, great video! One thing I don't understand though, it is said in the video that the certificate authority generates a hash from Alice's certificate signing request (city, state, country, etc...) then encrypts it with their private key. However, it is said that Bob creates a hash of ALL the information on the digital certificate (name of issuer, serial number, etc...). This info is not the same as the one from Alice's certificate signing request. So how can Bob get the same hash when it is generated from different info ?

@lolgaming-bq3vs 23 күн бұрын

alice send his into to the certificate authority : (eg) name , address and email CA (Certificate Authority) : create hash digest of alice's name , address and email then encrypt that hash digest with his own private key and write that down in alice certificate when bob receive alice cert then bob create hash digest of alice info (anme, address and email) from same algorithm and decrypt those hash using CA public key , if hash is same then right otherwise wrong here is in short form: alice to CA : name , address , email CA return alice : name ,address, email and a hash encrypted by CA's private key in form of digital *CERTIFICATE* alic to bob : DIGITAL CERTIFICATE bob verify :decrypt the hash using CA public key and match

@georgetsiklauri Жыл бұрын

00:24 What? You say, this: "If Bob can *decrypt* the message that came from Alice, using Alice's public key, then Bob knows that the message came from Alice." But how would Bob decrypt a message with Alice's public key? maybe you wanted to say, that Bob should encrypt (not decrypt) the message? Unclear. Public keys are shared because the receiver should be able to encrypt the data with that public key, not decrypt. For decryption, private key is there. Then you continue, that Alice encrypts the message with the private key.. man, I think you're using public and private keys really incorrectly here.

@mateiivan4416 9 ай бұрын

I think what they are saying here is that if you can decrypt the message with the public key of the sender, then it must have been them who have encrypted it because only they know their private key (which is called signing a message). If someone encrypted the message with your public key and sent it to you to decrypt with your private key, there would be no way to prove that they are who they say they are. So the initial approach must be taken to prove this, but it can be disrupted by an attacker. Thus, certificates must be used.

@merlinabraham9417 7 ай бұрын

Public key is used for encryption and private key is used for decryption. So alice sends Bob her private key not public.