Ohh yesssss. Whilst going through your TLS series got notification of this video and oh boy am I ready for Diffi. It’s not easy to understand but I can almost be certain you’ll have broke it down in such a way my 80 year old grandma will make sense of it!
I dont know how to say thankyou to this channel as it made me to understand all these complicated concepts in very simple explanation.... Good work & keep doing it 🙂
Renu! I've rather enjoyed seeing your kind comments on all the videos. Thank you for the positive energies! Truly happy you are learning so much from the channel. Cheers, friend. Happy (continued) learning! =)
Hey Ward, I just wanted to say a huge thank you for the Super Thanks donation! Your support truly brightens my day and motivates me to create even more content. Thank you!
Hey hey, tried with Private key =2 and Private key =7, ending up with Public key =10 and Public key =7. And Shared one is 10. Thank you for your work! You are the best 😎🤓
These videos are life changing, I appreciate your teaching style and notes! Question: Do you think we will go to elliptic curve crypto, away from DH and RSA due to key sizes etc, at least for key exchange? I would love to see you do a 101 video on ECC, as it's blowing my head around the maths and how it works!
Yes, it's on my list! EC crypto is just using a different set of "numbers" than what we are used to. IT's still the same algorithms, just using points on a curve instead of real numbers (1, 2, 5, 100, 9999, etc...). So yes, we will always be using DH, RSA, DSA, etc... just sometimes on a curve (hence ECDH, ECRSA, ECDSA). Well, at least until quantum safe algorithms take over, I suppose.
@@PracticalNetworking I'd love to see ECSDSA! Thankyou for making it so much easier to learn, I appreciate you so much. Do you think we will have quantum safe? Or "safe for now"? I wonder if that's measured in years, decades, or more?
How did they agree on two numbers, 13 and 6, at the beginning of their conversation? Let's say Bob doesn't know Alice and wants to send her a message. How will their first exchange happen? I am still confuse about it
In standard tls, a separate secret key is generated by the client and encrypted with servers public key is sent to the server. That is only the servers public/private key pair is used to exchange the symmetric key. Is that different than the secret key generation and sharing discussed here.
Cheers , made that a lot easier than most do . not an easy one to explain and welcome back Alice and Bob :) . These Martin Helman and Whitfield Diffie guys have some brain capacity don't they .
so DH negotiates session key to encrypt data symmetric. However, RSA generates key pairs that are used to encrypt the session key when exchanged? then that session key is used symmetric to encrypt bulk data?
Hi, what if the public key which Alice and Bob shares with each other is modified by hackers in public network? Both Alice and Bob would never be able to create same shared secret.
Yes! Correct. Hence, when sharing the Public Key, it's good to also implement something that also provides Integrity. This is why when you download a website's certificate (which includes a public key), the certificate also includes a Signature (providing Integrity and Authentication). More details on signatures here: ruclips.net/video/_zyKvPvh808/видео.html
So if hacker get to know what the shared numbers are meant for (i:e maybe hacker manages to read an email which have them listed), then hacker will also end up generating the same secret key, right?
Good question... I should write an article about it. Reach out to me on Discord and I can explain it to you briefly. But you are correct to point out Generator != Prime number. =)
6 being a generator of 13 in this context means that any number from 1 to 12 can be written as 6^k (mod 13) for some k between 1 and 12. Not only does the speaker not define what "generator" means, he then goes on to say that Alice and Bob each "generate" a private number without defining what that means. Indeed the private numbers can be "generated" in the sense above because a and b are constrained to be whole numbers between 1 and 12, and we have just seen that all such numbers can be "generated" by writing them as 6^k (mod 13). But surely it would have been simpler to say that Alice and Bob each choose an arbitrary whole number between 1 and 12.
Congrats Ayrad. You won the random course giveaway =). Reach out to me on Discord to claim your prize: pracnet.net/discord (I just realized that I never picked a Winner for this video, sorry for the long delay)
the ENTIRE so-called Security of Diffie Hellman, is dependent on the premise that an attacker would need THOUSANDS of years to brute force matching keys 🤔🤔🤔 And we HAVE lottery winners who can PERFECTLY pick a sequence of 7 numbers OUT of a staggering 60-number ball RANDOMIZING machine 🙄🙄 i hope these numbers of Mr Diffie are BIG enough to **prevent** this sort of LUCKY matches 🙄🙄 Now watch out for that word again . . . do big numbers (being RANDOM themselves 😟🧐😳) actually **PREVENT** random LUCKY matches from attackers 😰😰 ?
So, to bob and alice decrypte the message first, it must alice and bob accept the public key both side witch A=(G x mod n) the result is the public key must be accepted both side and we called this digital certificate.
![Noob To Max With DRAGON REWORK In Blox Fruits [FULL MOVIE]](http://i.ytimg.com/vi/LnBMOinoOvA/mqdefault.jpg)
📢 *Black Friday / Cyber Monday Promotion*
👉 Practical TLS for only $50 (originally $297)
💻 Use code *BFCM2024* --> pracnet.net/tls
📅 Offer expires Dec 6
This was by far the easiest example on RUclips for understanding Diffie-Hellman. Thanks!
Glad you enjoyed it =)
agreed!
Probably the best video on Diffie-Hellman algorithm, so well done!
Thank you for this series, It's really well made. I would probably reference each time I forget a concept.
Glad you enjoyed it!
That is exactly what I was looking for a while. I also signed up for the TLS course. Well done for the great content.
Ohh yesssss. Whilst going through your TLS series got notification of this video and oh boy am I ready for Diffi. It’s not easy to understand but I can almost be certain you’ll have broke it down in such a way my 80 year old grandma will make sense of it!
Hope it lived up to your expectation!
I dont know how to say thankyou to this channel as it made me to understand all these complicated concepts in very simple explanation.... Good work & keep doing it 🙂
Renu! I've rather enjoyed seeing your kind comments on all the videos. Thank you for the positive energies! Truly happy you are learning so much from the channel. Cheers, friend. Happy (continued) learning! =)
Perfect simplest explanation found on youtube
Thanks!
Hey Ward, I just wanted to say a huge thank you for the Super Thanks donation! Your support truly brightens my day and motivates me to create even more content. Thank you!
Hey Ed,
as I['ve ]read through them: You really earn these praises here. Thank you!
Best regards,
CC.
Hey hey, tried with Private key =2 and Private key =7, ending up with Public key =10 and Public key =7. And Shared one is 10. Thank you for your work! You are the best 😎🤓
Another great monday. Thanks for the upload
You're welcome! Glad you liked it!
I have to subscribe to this channel. Thank you.
Just liked it before watching, we all know it's gonna be a great Video
;)
These videos are life changing, I appreciate your teaching style and notes!
Question: Do you think we will go to elliptic curve crypto, away from DH and RSA due to key sizes etc, at least for key exchange?
I would love to see you do a 101 video on ECC, as it's blowing my head around the maths and how it works!
Yes, it's on my list!
EC crypto is just using a different set of "numbers" than what we are used to. IT's still the same algorithms, just using points on a curve instead of real numbers (1, 2, 5, 100, 9999, etc...).
So yes, we will always be using DH, RSA, DSA, etc... just sometimes on a curve (hence ECDH, ECRSA, ECDSA).
Well, at least until quantum safe algorithms take over, I suppose.
@@PracticalNetworking I'd love to see ECSDSA!
Thankyou for making it so much easier to learn, I appreciate you so much.
Do you think we will have quantum safe? Or "safe for now"? I wonder if that's measured in years, decades, or more?
Everything in crypto is always a "safe for now" gamble ;p
You are a great teacher!
How did they agree on two numbers, 13 and 6, at the beginning of their conversation? Let's say Bob doesn't know Alice and wants to send her a message. How will their first exchange happen? I am still confuse about it
The peers have to do a handshake before they can do DH, and in that handshake they "agree" on a DH Group (which contains the two numbers, P and G).
no one will overhear this?
@rotorfpv4117 They will, but without knowing either peers private key, it's safe.
@@rotorfpv4117anyone can overhear, but they won't be able to calculate the shared key cause it depends on the secret keys, which are secret
Thank you for Teaching very easily understand difficult concept.
You're welcome, Karthik!
CA certificates contain publicPrivate keyPairs stamped by a trusted authority.......Great Course ED.... well done
Thanks for supporting the channel =)
As always, very great lecture, very useful, thank you so much brother
You're welcome!
Like always, you make it look easy. Thanks
You're welcome, Azza!
so damn good course. I am registering the course. Keep good work, Ed!
In standard tls, a separate secret key is generated by the client and encrypted with servers public key is sent to the server. That is only the servers public/private key pair is used to exchange the symmetric key.
Is that different than the secret key generation and sharing discussed here.
Cheers , made that a lot easier than most do . not an easy one to explain and welcome back Alice and Bob :) . These Martin Helman and Whitfield Diffie guys have some brain capacity don't they .
Yea, it's incredible that these algorithms were developed 30~ years ago and are still the foundation of the crypto we use today. Cheers Don!
Excellent explanation. 👍
Thank you!
Perfect explanation.
OK, nice explanation. What i can never find is how the keys are used to crypt and decrypt messages! Do you have some ressources on that by a chance?
Yes, I have a video on my channel about RSA. It shows the math which creates keys, and the math which uses them to encrypt and decrypt messages.
Many Thanks for your Amazing topics, keep it up
Thank you so much :)
As Always, Great!
You're welcome, Hosein =)
so DH negotiates session key to encrypt data symmetric. However, RSA generates key pairs that are used to encrypt the session key when exchanged? then that session key is used symmetric to encrypt bulk data?
The math in this one is very cool :)
Agreed =)
Thanks for the excellent video.
Hi, what if the public key which Alice and Bob shares with each other is modified by hackers in public network? Both Alice and Bob would never be able to create same shared secret.
Yes! Correct. Hence, when sharing the Public Key, it's good to also implement something that also provides Integrity. This is why when you download a website's certificate (which includes a public key), the certificate also includes a Signature (providing Integrity and Authentication).
More details on signatures here:
ruclips.net/video/_zyKvPvh808/видео.html
So by this "integrity" mechanism they will both know IF the public key they received was tampered or not? Cool!
hello how are the agreed number defined to be used bu both parties?
So if hacker get to know what the shared numbers are meant for (i:e maybe hacker manages to read an email which have them listed), then hacker will also end up generating the same secret key, right?
Thank you sir,, best video.
You're welcome!
Thank you !
Thank you, this helped a lot!
Glad to hear!
Well done... Thanks a lot..
But what exactly is Generator of P? Is it randomly generating Prime numbers or just random numbers? In this case 6 is not a Prime number
Good question... I should write an article about it. Reach out to me on Discord and I can explain it to you briefly.
But you are correct to point out Generator != Prime number. =)
is this algorithm refers to the hybrid key cryptography
6 being a generator of 13 in this context means that any number from 1 to 12 can be written as 6^k (mod 13) for some k between 1 and 12. Not only does the speaker not define what "generator" means, he then goes on to say that Alice and Bob each "generate" a private number without defining what that means. Indeed the private numbers can be "generated" in the sense above because a and b are constrained to be whole numbers between 1 and 12, and we have just seen that all such numbers can be "generated" by writing them as 6^k (mod 13). But surely it would have been simpler to say that Alice and Bob each choose an arbitrary whole number between 1 and 12.
Very cool, thank you!
Thank you man for the video :)
You're welcome, Ayrad!
Congrats Ayrad. You won the random course giveaway =). Reach out to me on Discord to claim your prize: pracnet.net/discord
(I just realized that I never picked a Winner for this video, sorry for the long delay)
@@PracticalNetworking thank you very much :)
@@PracticalNetworking I'm in your groupe in discord but I don't know how to get what I have won :D
SpongeBob and cryptography 🔐 are a FANTASTIC pair!
Agreed ;)
Super!!
=)
Thank you :)
Aha! So they exchange each other's public but they don't see each other's private! Got it!
Exactly. =)
+1 for the 'why' it is difficult te reverse engineer!
Am I the only one to feel this topic is just a piece of cake after hearing this explanation?
That tells me I did my job correctly =).
@@PracticalNetworking absolutely, just love your videos.
@@safwanumer3997 If you're willing, sharing this content online would be a great help. =) Glad you enjoyed these either way. Cheers, Safwan.
Sanks q very much
You're welcome Eric.
Que vídeo do caralho.. nunca encontrei um vídeo no RUclips com tamanha qualidade de detalhes..
sometimes i just wish i can give u a thousand likes with one account. #Simplified learning
Thanks for the kind note =). I appreciate even the single like! Cheers.
👍👍👍
👏👏👏✅
=)
the ENTIRE so-called Security of Diffie Hellman, is dependent on the premise that an attacker would need THOUSANDS of years to brute force matching keys 🤔🤔🤔 And we HAVE lottery winners who can PERFECTLY pick a sequence of 7 numbers OUT of a staggering 60-number ball RANDOMIZING machine 🙄🙄 i hope these numbers of Mr Diffie are BIG enough to **prevent** this sort of LUCKY matches 🙄🙄 Now watch out for that word again . . . do big numbers (being RANDOM themselves 😟🧐😳) actually **PREVENT** random LUCKY matches from attackers 😰😰 ?
So, to bob and alice decrypte the message first, it must alice and bob accept the public key both side witch A=(G x mod n) the result is the public key must be accepted both side and we called this digital certificate.