Glad this is helping you, Ray. Good luck w/ your Net+ =) You might also enjoy the Networking Fundamentals series: ua-cam.com/play/PLIFyRwBY_4bRLmKfP1KnZA6rZbRHtxmXi.html That said... if you are willing... Could you do me a favor? Do you mind sharing this video on Linked In, Reddit, Twitter, Facebook, or any other social media you use? As an independent creator, that would be an _enormous_ help, and I would appreciate it _greatly_ .
Really enjoying the videos & contents.... good part is to keep viewer engage with interesting & simple explanation to understand the problems in hand when send anything over the wire... Every developer should understand these concept as it is equally important as build any application.... 🙂
Great video! But I have a question: To my understanding, non-repudiation ensures that neither party can deny participance in parts of, or all of the communication. But how does this prove that the specified destination of the message actually recieved the datagram?
If the message was never received, there would be no claim that a message was sent. i.e., for someone to accuse a sender of sending a message, the message _has_ to have arrived on the other side.
@@simeneidal5203 Glad you've enjoyed them, Simen. As always, sharing the content really goes a long way and helps me out. If you're willing, please consider it =).
QUESTION about non-repudiation: Only the server is server (e.g. web server) is authenticated in the process of TLS, not the client (e.g. browser). So I think non-repudiation only applies to the server but not the client. Is it right?
Thanks a lot for the great job sir, Please i have an important question, it is about the anti-replay scenario, well TLS provide authentication and integrity, so i guess that the bank HQ will know that the red person is sending forged messages (i.e. he has not the real authentication), please i want to know how is he able to send these duplicate of the second packet. I appreciate your amazing work and the time to read my comment.
With SSL/TLS, after the packets are encrypted they are passed from one ISP to another until they get to their destination. There is nothing stopping someone from working at the ISP to simply copy the packets on the wire and send them along a second or third time. More details on how encrypted packets are sent across the Internet here: ua-cam.com/video/HMoFvRK4HUo/v-deo.html
@@Mohamed-Maghrebi You're very welcome. If you enjoyed this video and/or the rest of the series, consider sharing it with a friend or community online. =) No worries either way though, cheers Mohamed!
TLS does not provide non-repudiation! Because the authentication is only on the connection itself and not on every single message. This is done by sharing a symmetric key, which enables both sides to encrypt and sign messages. Doing this does not break anything because as long as one side does not lie to itself, it will know what messages are sent by the other.
📢 *Black Friday / Cyber Monday Promotion*
👉 Practical TLS for only $50 (originally $297)
💻 Use code *BFCM2024* --> pracnet.net/tls
📅 Offer expires Dec 6
You're the best UA-cam channel for understanding the networking concept brother your are the best thanks for this ❤
Thank you for the kind words =)
Ty for your time and expertise on this subject. Clear, precise and accurate
Studying for Network+. This channel is basically an Ivy League School! Thanks for the free knowledge
Glad this is helping you, Ray. Good luck w/ your Net+ =)
You might also enjoy the Networking Fundamentals series: ua-cam.com/play/PLIFyRwBY_4bRLmKfP1KnZA6rZbRHtxmXi.html
That said... if you are willing... Could you do me a favor? Do you mind sharing this video on Linked In, Reddit, Twitter, Facebook, or any other social media you use? As an independent creator, that would be an _enormous_ help, and I would appreciate it _greatly_ .
Great explanation! this helped me understand both terms. Thanks!
Really enjoying the videos & contents.... good part is to keep viewer engage with interesting & simple explanation to understand the problems in hand when send anything over the wire... Every developer should understand these concept as it is equally important as build any application.... 🙂
you are a saint for these videos thank you
short and sweet. great explanation
You = Teacher material
Thank you again, Hamza =)
Great lesson!
Thanks, Ward.
One of the best video
Thank you again, Chaithanya =)
Thank you for your work!
You're welcome again, Alitta =)
Thanks for this video.
Great video! But I have a question:
To my understanding, non-repudiation ensures that neither party can deny participance in parts of, or all of the communication. But how does this prove that the specified destination of the message actually recieved the datagram?
If the message was never received, there would be no claim that a message was sent. i.e., for someone to accuse a sender of sending a message, the message _has_ to have arrived on the other side.
@@PracticalNetworking I see, thank you for answering my question. Loving your videos!
@@simeneidal5203 Glad you've enjoyed them, Simen. As always, sharing the content really goes a long way and helps me out. If you're willing, please consider it =).
Super interesting.
QUESTION about non-repudiation:
Only the server is server (e.g. web server) is authenticated in the process of TLS, not the client (e.g. browser). So I think non-repudiation only applies to the server but not the client. Is it right?
Thanks a lot for the great job sir,
Please i have an important question, it is about the anti-replay scenario, well TLS provide authentication and integrity, so i guess that the bank HQ will know that the red person is sending forged messages (i.e. he has not the real authentication), please i want to know how is he able to send these duplicate of the second packet. I appreciate your amazing work and the time to read my comment.
With SSL/TLS, after the packets are encrypted they are passed from one ISP to another until they get to their destination. There is nothing stopping someone from working at the ISP to simply copy the packets on the wire and send them along a second or third time.
More details on how encrypted packets are sent across the Internet here:
ua-cam.com/video/HMoFvRK4HUo/v-deo.html
@@PracticalNetworking Thanks a lot sir, i appreciate your amazing work, you made it clear for me now
@@Mohamed-Maghrebi You're very welcome.
If you enjoyed this video and/or the rest of the series, consider sharing it with a friend or community online. =) No worries either way though, cheers Mohamed!
Yes of course 🙌🏻
@@Mohamed-Maghrebi Thank you for your support. =)
TLS does not provide non-repudiation!
Because the authentication is only on the connection itself and not on every single message.
This is done by sharing a symmetric key, which enables both sides to encrypt and sign messages. Doing this does not break anything because as long as one side does not lie to itself, it will know what messages are sent by the other.
Integrity does not prevent the modification of the data, it is a property that notifies when the data is modified
Thanks for this great video :)
You're welcome, Virender =). Glad you enjoyed it!
why are you not making videos frequently..they are good..
amazing
👍👍👍
👍