This is by far the most simple explanation of the presented concepts - in a way that everyone understands it and from then can move on to the more complicated parts. Excellent.
Done thanks 0:15 explaining RSA 1:30 digital signatures: it doesn’t matter what key we encrypt with (public or private) the message can only be decrypted with the other key. A message can be digitally signed by encrypting it with the private key and then others can verify the signature by decrypting with public key. 3:58 digital signature example 5:40 sender hashes the message, encrypts the hash with their private key. Receiver decrypts the hash with the sender’s public key, and if it matches the message then receiver knows message came from sender 7:00 why we need digital certificates on top of digital signatures. Someone could be pretending to be the sender, and digitally signs the message. The receiver has no way of verifying the sender’s identity. Digital certificates is how the receiver can verify that a public key actually belongs to the sender 8:00 how certificate authority works
Studying for CCNA Cyberops , the Cisco documentation on this is a complete mess. This video is pure gold , incredibly simple and clear. Thank you sir , keep up the great work . On more subscriber for your great channel :)
Thank you for simplifying the concept of digital keys and explaining the role of hashing in it. Your explanation has made it easy for anyone to understand these complex theories.
@@ComputerScienceLessonsthe explanation is phenomenal sir. I wish you could make more videos on cybersecurity topics esp security+. I'd gladly join your patteon
This video is really nice! However there is one part I can't wrap my head around. From my understanding: 1: Person A types a message 2: Person A generates a hash of the message using sha 3: Person A encrypts the generated hash using their private key 4: Person A appends the encrypted hash to the message as a signature, and sends it to person B 5: Person B receives the message along with the signature 6: Person B decrypts the signature (encrypted hash) using person A's public key 7: Person B runs sha on the message to generate a hash. 8: Person B compares the resulting hash from the message to the hash from decrypting the signature 9: If they are the same, it;s been verified successfully. So, what's the point of the sha layer exactly? Why not simply add the message encrypted with person A's private key as a signature? In both cases only person A's public key would be able to decrypt it so I can't see how running it through sha would make a difference.
Nice question. One of the key features of a hash algorithm is that it produces a hash value of a fixed size. SHA256 for example will produce a hash value that is always 256 bits long, no matter how big the original message. This ensures that the digital signature is a manageable size, regardless of the document being signed. You might like my series on cryptocurrency which also explains the benefits of hashing. th-cam.com/play/PLTd6ceoshprd7UngbhRHMgKXcWz4PIBEe.html :)KD
This functionality is built into software such as a web browser. Jill will get a message like 'could not logon' or 'transaction failed' depending on what she is trying to do. :)KD
In asymmetric cryptography, there are two keys: a public key and a private key. Each key has a specific role: Encryption: Typically, the public key is used to encrypt data. The corresponding private key is used to decrypt the data. Decryption: Only the private key can decrypt the data encrypted with the public key. However, the roles can be reversed in a different context, such as digital signatures: Signing: The private key is used to create a digital signature. The public key is used to verify the signature.
6:44 What is the use of encrypting the hash value here using BOB Private key and sending, As however it can be decrypted by BOB's public key which is available to everyone You can directly send the hash value or use Gill public key and encrypt and send right?
Hi Tom. The public and private keys are created together. They are mathematically related, very large, numbers. They are useless without each other and cannot be created independently of each other (without an impractical amount of computation - or a quantum computer). This video should clear up the relationship between the keys... :)KD th-cam.com/video/cKWA8f7xdL8/w-d-xo.html
This is really a great explanation, Question: If we talk about a real scenario, A client browser want to access some webpage and send a request, what would be the actual message first time from client and what will be the revert from the server? In the example, The message is the actual document but what would be in the actual scenario? is it certificate itself from the web server?, that's what I can guess.
Does Jill contact the certificate authority to make sure the public key on the certificate (that is sent to her by jack) is the same as the one in the certificate authorities database? If not, surely the digital certificate could just be ‘forged’
never having worked with this stuff I really don't understand. jack presents his public key along with the digest and puts it in a digital certificate. Jill trusts this because she trusts the 3rd party that "vouched" for jack. I get that in a very generic sense. but what exactly does jill see when she compares the certificate to whatever she sees when she queries the certification authority?
Hopefully, nothing. The process is carried out by the web browser in the background. If there's a problem she may see a message saying the websites certificate in invalid. (double click the little padlock in your browser's address bar). :)KD
Encrypted communications are typically managed automatically by the software being used by the people communicating. The cryptosystem being used is built into the software. For example, when we buy things online, our web browser and the sellers webserver take care of everything for us. :)KD
if someone was in the middle of a digital signature between person a and b couldnt they(person m) hash the email/text and sign it with their own key and send that to person b. Then when person b sends an email back to a, person m can hash the email and send a resigned version back to a?
Is the Digital Certificate embedded in the document that is being sent or attached to the email message with the document? What prevents a bad guy from obtaining a copy of someone else's digital certificate and using it to pass himself off as the rightful owner of the digital certificate?
I'm still unclear on how asymmetric encryption works. It makes sense when you use the public to encrypt and the private key to decrypt. But if A sent a message to B and used the private key to encrypt it and B will use the public key to decrypt it, what would stop C from intercepting the message and using the public key to decrypt it? Or is it a situation where you *can* use the private key to encrypt and the public key to decrypt, but you wouldn't because then anyone with the public key could decrypt it?
You are correct. The public key is used to encrypt the message and the private key yo decrypt it. It's like me sending you a box with an open padlock, but keeping the key to myself. You could lock something inside the box and send it back to me (locked). Only I have the key. Have you watched this one yet? th-cam.com/video/mjWTU-hRmyg/w-d-xo.html :)KD
sorry to bother you after 2-3 years mate but in the video it's explicitly mentioned multiple times throughout, that the senders and receivers "really do not care if anyone sees the message" because the public key is...well..public [and that they just want to verify each other's identities] what happens if we do care about people snooping then? if A encrypts a secret message with their private key then sends it to B, how can they be sure that no C or D intercepts them and reads A's message instead. (or is secure data transmission a completely different topic and not related to key encryption whatsoever?) or is just the fact that we simply never use our/the sender's private keys to encrypt outgoing messages and that we instead use the receiver's public key instead? ,so in our case A uses B's public key to encrypt his secret message so that B and only B can read it with their private key? (actually I think this is it and I regret asking the stupid stuff above but it'd be nice if someone could verify this info)
This is a tricky concept to get your head around if you are new to it. You seem to have got it... If I wanted to send YOU an encrypted message, then you would create the public and private keys, and send me your public key. When I receive your public key, I would use it to encrypt my message, and I would send you the ciphertext. Only YOU possess the matching private key, so only YOU can decrypt the message. This all happens automatically when we use a web browser to connect to a secure website. You may find this interesting... th-cam.com/video/mjWTU-hRmyg/w-d-xo.html and this... th-cam.com/video/cKWA8f7xdL8/w-d-xo.html :)KD
This is by far the most simple explanation of the presented concepts - in a way that everyone understands it and from then can move on to the more complicated parts. Excellent.
this is the only video you need to watch if you want a practical understanding of digital signatures
Wow! This might be the best video on data integrity and data authentication
- digital signatures rely on asymmetric cryptography.
Such an explanation with downgraded complexity, but with an upgraded realization. Exceptionally wonderful.
Thank you :)KD
This is the single best illustration/explanation of this concept on the internet. Keep making these videos man, you've got talent.
Thank you :)KD
Done thanks
0:15 explaining RSA
1:30 digital signatures: it doesn’t matter what key we encrypt with (public or private) the message can only be decrypted with the other key. A message can be digitally signed by encrypting it with the private key and then others can verify the signature by decrypting with public key.
3:58 digital signature example
5:40 sender hashes the message, encrypts the hash with their private key. Receiver decrypts the hash with the sender’s public key, and if it matches the message then receiver knows message came from sender
7:00 why we need digital certificates on top of digital signatures. Someone could be pretending to be the sender, and digitally signs the message. The receiver has no way of verifying the sender’s identity.
Digital certificates is how the receiver can verify that a public key actually belongs to the sender
8:00 how certificate authority works
2 days on the internet trying to understand this subject , your 11 min video made it , thank you alot !
Glad to be of service :)KD
Used this video to get my Sec+ a few years back now... Back to refresh myself on this for my SSCP. Awesome video. Thank you so much!
Studying for CCNA Cyberops , the Cisco documentation on this is a complete mess. This video is pure gold , incredibly simple and clear. Thank you sir , keep up the great work . On more subscriber for your great channel :)
Exactly here for the same reason, good luck on you exam.
You deserve an Oscar for that kind of explanation .
Thank you. I'll start writing my speech. :)KD
Thank you for simplifying the concept of digital keys and explaining the role of hashing in it. Your explanation has made it easy for anyone to understand these complex theories.
You are most welcome :)KD
Perfect! At 6:19 I first thought you made a mistake but after finnishing the whole video you carefully explain how a CA works. Brilliant. Thank you.
You are very welcome.
I love the narration, the humour, the analogies and the simple and easily understandable format. Thank you!
You are most welcome :)KD
@@ComputerScienceLessonsthe explanation is phenomenal sir. I wish you could make more videos on cybersecurity topics esp security+. I'd gladly join your patteon
This is the best explanation of digital certificates and digital signature i have come across. Thank you :)
Thank you :)KD
You have talent to explain concepts...Thank you
You're very kind. Thanks for the comment. :)KD
It's crystal clear the way you explain and demonstrate with animation.
Thank you :)KD
This channel is underrated!
Thank you :)KD
Amazing teaching. After viewing this video, finally I can understand the concept clearly.
Thanks for this amazing video, it helped me understand digital signature more better
10 from 10! so easy to understand, A good lesson for other TH-camrs talking about Digital Signature!
wow! that is very well made. direct, clear and no annoying repetitions
Thank you :)KD
you took 10 minutes to teach me whatever my teacher trying to teach me in 3 hours, damn !!!
Glad to help :)KD
Finally, thank you so much I've been trying to understand this for a while now.
You're most welcome. :)KD
This is by far the best explanation i've ever seen of this. Thanks a lot :D.
THanks so much for this video, Fought hours to understand this
fabulous explanation, simple and clear.
What a brilliant work !
Finally, you explain it crystal clear! Thanks you very much!
You're most welcome. Thanks for commenting :)KD
Thank for this breakdown, it gave me a better understanding of the entire concept.
You are most welcome :)KD
I cannot thank you enogh for this video.
You explained it without extra info
Thanks alot 👍👍👍
You welcome. Thanks for the lovely comment. :)KD
finally, someone who puts it clearly and totally
Thanks for the comment. Really appreciated. :)KD
Best video about digital certificates ever.
Thank you so much :)KD
Excellent!! Explained in such a simple way. Thanks!
Thank you too :)KD
exceptionally clear and easy to understand
Thank you :)KD
i just saw this one video, but this is enough reason to subscribe. whatever you post I'm gonna watch it. damn
Welcome aboard :)KD
Very good and clear explanation.
This is so lucid. Beautifully explained
Thank you :)KD
I think I attained Nirvana after watching this!
Thank you!!
It's been a while since I've done that for anyone. You are very welcome :)KD
This is best and simplest explanation. Thanks
Love this video. 100 out of 10 ( ten, yes ), you deciphered it properly.
Thank you so much :)KD
Finally I got this concept!!! Thanks!!
Delighted to help - it's actually a brilliantly simple idea isn't it!? :)KD
Best explanation ever. Thank you Sir.
Thanks for the video. Keep up the good work 👍
Really great video! Explained the things clearly.
Delighted to help :)KD
This video is really nice! However there is one part I can't wrap my head around. From my understanding:
1: Person A types a message
2: Person A generates a hash of the message using sha
3: Person A encrypts the generated hash using their private key
4: Person A appends the encrypted hash to the message as a signature, and sends it to person B
5: Person B receives the message along with the signature
6: Person B decrypts the signature (encrypted hash) using person A's public key
7: Person B runs sha on the message to generate a hash.
8: Person B compares the resulting hash from the message to the hash from decrypting the signature
9: If they are the same, it;s been verified successfully.
So, what's the point of the sha layer exactly? Why not simply add the message encrypted with person A's private key as a signature? In both cases only person A's public key would be able to decrypt it so I can't see how running it through sha would make a difference.
Nice question. One of the key features of a hash algorithm is that it produces a hash value of a fixed size. SHA256 for example will produce a hash value that is always 256 bits long, no matter how big the original message. This ensures that the digital signature is a manageable size, regardless of the document being signed. You might like my series on cryptocurrency which also explains the benefits of hashing.
th-cam.com/play/PLTd6ceoshprd7UngbhRHMgKXcWz4PIBEe.html
:)KD
Great job 👍 amazing explanation 👏 thank you so much .
You're very welcome. 😳 :)KD
Thank you for that. The certification authority is the bit missing from most other explanations!
You are very welcome. :)KD
Best explanation I have seen!😁
Thank you :)KD
@6:12 If How does Jill know that she cannot decrypt Jacks signature with his Public Key? Does the attempted decryption show a 'fail' message or code?
This functionality is built into software such as a web browser. Jill will get a message like 'could not logon' or 'transaction failed' depending on what she is trying to do. :)KD
@@ComputerScienceLessons Thanks, this video was helpful!
Best explanation ever ❤ thanks bro
Thank you so much :)KD
Wts thats just genius 👏 how people come out with these stuff
Such a clear explanation - thank you !
Great Explanation! Much appreciated
You're very welcome :)KD
Thank you very much for clearing the concept
You are most welcome :)KD
In asymmetric cryptography, there are two keys: a public key and a private key. Each key has a specific role:
Encryption:
Typically, the public key is used to encrypt data.
The corresponding private key is used to decrypt the data.
Decryption:
Only the private key can decrypt the data encrypted with the public key.
However, the roles can be reversed in a different context, such as digital signatures:
Signing:
The private key is used to create a digital signature.
The public key is used to verify the signature.
Nice way of explaining through graphics....
Very impressive explanation
simple explanation. all i can say is wow!!!!
Thank you :)KD
6:44 What is the use of encrypting the hash value here using BOB Private key and sending, As however it can be decrypted by BOB's public key which is available to everyone
You can directly send the hash value or use Gill public key and encrypt and send right?
1:36 Isn't the public key derived from the private key? If someone has a private key can't they generate the public key themselves?
Hi Tom. The public and private keys are created together. They are mathematically related, very large, numbers. They are useless without each other and cannot be created independently of each other (without an impractical amount of computation - or a quantum computer). This video should clear up the relationship between the keys... :)KD
th-cam.com/video/cKWA8f7xdL8/w-d-xo.html
Good freaking job mate, thanks.
TY :)KD
great content. I wonder if it calculates different hash for different data so digital signature is changed everytime on certificates or not ?
Wonderful video!! Thanks a lot for great explanation
You're most welcome. Thanks for the lovely comment. :)KD
Amazing explanation TQ
You're most welcome :)KD
That was all I ever needed thank you so much for explaining with that great tone!
You made my day :)
Thanks for the complement :)KD
This is really a great explanation, Question: If we talk about a real scenario, A client browser want to access some webpage and send a request, what would be the actual message first time from client and what will be the revert from the server?
In the example, The message is the actual document but what would be in the actual scenario? is it certificate itself from the web server?, that's what I can guess.
Awesome explanation.best video found on this topic
Thank you.
Lovely work well done.
Thank you. Lovin' your name :)KD
This is Bob, Bob is builder !!! caught me so off guard ahahhaahah
He says he's a builder, but he's really a con artist :)KD
Amazing explanation. Thanks
Does Jill contact the certificate authority to make sure the public key on the certificate (that is sent to her by jack) is the same as the one in the certificate authorities database? If not, surely the digital certificate could just be ‘forged’
the certificate is signed by the CA. if the signature isn't valid it's forged
never having worked with this stuff I really don't understand. jack presents his public key along with the digest and puts it in a digital certificate. Jill trusts this because she trusts the 3rd party that "vouched" for jack. I get that in a very generic sense. but what exactly does jill see when she compares the certificate to whatever she sees when she queries the certification authority?
Hopefully, nothing. The process is carried out by the web browser in the background. If there's a problem she may see a message saying the websites certificate in invalid. (double click the little padlock in your browser's address bar). :)KD
How does the receiver know that she has to use SHA 256? Are these agreed before?
Encrypted communications are typically managed automatically by the software being used by the people communicating. The cryptosystem being used is built into the software. For example, when we buy things online, our web browser and the sellers webserver take care of everything for us. :)KD
Thank you so much!!!! This was SOO helpful.
You are very welcome :)KD
Very well explained
Thank you :)KD
For the past fews months I'm looking for something on cryptography and i found this finally thanks
if someone was in the middle of a digital signature between person a and b couldnt they(person m) hash the email/text and sign it with their own key and send that to person b. Then when person b sends an email back to a, person m can hash the email and send a resigned version back to a?
Best video on the topic
Thank you :)KD
outstanding video
The presentation is really clean.
Thank you :)KD
Excellent lesson!
Thank you :)KD
great explanation
Thank you. You might like my crypto videos :)KD
Ugh, this is great thank you so much!
You're welcome. :)KD
so we use the same private key to encrypt data as well as to sign or better use different pairs?
great explanation. If the message was intended to be confidential, wouldn't Jack want to encrypt the message with Jill's public key?
fantastic channel i love it
Thank you. That's music to my ears :)KD
Good content 🙂
Thank you :)KD
Is the Digital Certificate embedded in the document that is being sent or attached to the email message with the document? What prevents a bad guy from obtaining a copy of someone else's digital certificate and using it to pass himself off as the rightful owner of the digital certificate?
Good Explanation
Thank you :)KD
excellent explanation!!!
Thanks for saying so. :)KD
If the public key has the algorithm to encrypt a message if someone has the same public key can't he reverse engineer it and decrypt it?
I'm still unclear on how asymmetric encryption works. It makes sense when you use the public to encrypt and the private key to decrypt. But if A sent a message to B and used the private key to encrypt it and B will use the public key to decrypt it, what would stop C from intercepting the message and using the public key to decrypt it? Or is it a situation where you *can* use the private key to encrypt and the public key to decrypt, but you wouldn't because then anyone with the public key could decrypt it?
You are correct. The public key is used to encrypt the message and the private key yo decrypt it. It's like me sending you a box with an open padlock, but keeping the key to myself. You could lock something inside the box and send it back to me (locked). Only I have the key. Have you watched this one yet? th-cam.com/video/mjWTU-hRmyg/w-d-xo.html :)KD
@@ComputerScienceLessons than why does jill use private key to encrypt?
@@ComputerScienceLessons but you are saying sompletely different thing in the video mate.
This is Gold!
Thanks. I appreciate the comment. :)KD
Excellent video!!!
Thx :) KD
The research has came to an end
Amazing explanation :-)
Thank you :)KD
if a document has a esignature such as a letter but after someone else needs to add a date, how can this been done.
If you change the document, you lose the signature. You would need to sing it again.
sorry to bother you after 2-3 years mate but in the video it's explicitly mentioned multiple times throughout, that the senders and receivers "really do not care if anyone sees the message" because the public key is...well..public [and that they just want to verify each other's identities]
what happens if we do care about people snooping then? if A encrypts a secret message with their private key then sends it to B, how can they be sure that no C or D intercepts them and reads A's message instead.
(or is secure data transmission a completely different topic and not related to key encryption whatsoever?)
or is just the fact that we simply never use our/the sender's private keys to encrypt outgoing messages and that we instead use the receiver's public key instead? ,so in our case A uses B's public key to encrypt his secret message so that B and only B can read it with their private key? (actually I think this is it and I regret asking the stupid stuff above but it'd be nice if someone could verify this info)
This is a tricky concept to get your head around if you are new to it. You seem to have got it... If I wanted to send YOU an encrypted message, then you would create the public and private keys, and send me your public key. When I receive your public key, I would use it to encrypt my message, and I would send you the ciphertext. Only YOU possess the matching private key, so only YOU can decrypt the message. This all happens automatically when we use a web browser to connect to a secure website.
You may find this interesting...
th-cam.com/video/mjWTU-hRmyg/w-d-xo.html
and this...
th-cam.com/video/cKWA8f7xdL8/w-d-xo.html
:)KD
@@ComputerScienceLessons thanks a lot, love your channel, keep it up 👍
this is the easiest explanation , because the author used the stories and pics.
Glad you like my pics.
Very nice explaination. Only one questions, can a hacker make a fake digital certificate ?
Sadly yes. You could set up a fake certification authority. :)KD
Ok, thanks for the reply :)