Let's FIX a BROKEN TLS Handshake // with Wireshark

Поделиться
HTML-код
  • Опубликовано: 28 май 2024
  • A client reached out and said that some clients were able to connect to a secure application and others were not. Let's peek at the handshake and see what happened. (pcap used with permission)
    Got questions? Let's get in touch.
    LinkedIn: / cgreer
    RUclips: / chrisgreer
    Twitter: / packetpioneer
    == More On-Demand Training from Chris ==
    ▶Getting Started with Wireshark - bit.ly/udemywireshark
    ▶Getting Started with Nmap - bit.ly/udemynmap
    == Live Wireshark Training ==
    ▶TCP/IP Deep Dive Analysis with Wireshark - bit.ly/virtualwireshark
    == Private Wireshark Training ==
    Let's get in touch - packetpioneer.com/product/pri...
    //TLS Course from Practical Networking//
    Want to go deeper into TLS? Check out my buddy Ed's course:
    classes.pracnet.net/courses/p...
    Links above contain affiliate links where I will receive a small amount for any goods purchased. I thank you for clicking because it really helps to support me!!
    0:00 Intro
    0:28 TLS Client Hello
    1:36 Fatal TCP Error
    2:04 TLS Protocol Versions
    2:46 Why TLS 1.0?
    3:37 Conclusion
  • НаукаНаука

Комментарии • 47

  • @cristobalvalladares973
    @cristobalvalladares973 Год назад

    You sir are a godsend. Thank you. I'm a network engineer switching to security. My first view of Wireshark left me in shock. Your videos are helping me to get a better picture. Less shock now. Thanks!

  • @brianmurray8943
    @brianmurray8943 2 года назад +5

    This was good stuff. You should do one on IKEv1 vs IKEv2, and Ike with NAT-T with asynchronous agreement.

    • @ChrisGreer
      @ChrisGreer  2 года назад +4

      Oh nice suggestion. hey if I can find the pcaps, I'll do it! Any you got? 🙃

  • @TheSprog67
    @TheSprog67 Год назад

    Thanks to watching this I managed to spot a TLS problem saving me hours, mine was a "Fatal Handshake Failure", Many thanks Chris keep up the excellent work :)

  • @vyasG
    @vyasG 2 года назад +2

    Excellent Video. These real world examples are very valuable. Thank you so much. Do you have or plan to make any content on wireless Troubleshooting?

    • @ChrisGreer
      @ChrisGreer  2 года назад +1

      Thanks Vyas. I don't have any plans for wireless analysis. It's not really in my wheelhouse.

  • @AlejandroRodriguez-wt2mk
    @AlejandroRodriguez-wt2mk Год назад

    Nicely done.

  • @abdirahmanabdullahi1150
    @abdirahmanabdullahi1150 2 года назад +1

    Chris you show as what universities didn’t teach before thank you very much legend

  • @MrBitviper
    @MrBitviper Год назад

    awesome stuff as always chris
    when it comes to learning about wireshark and packet analysis you're the go to guy
    keep up the good work and keep em coming

  • @homayounshokri5041
    @homayounshokri5041 2 года назад +2

    Excellent
    can you make videos on DNS traffic analysis ?

  • @sri9277
    @sri9277 2 года назад

    Thank you for good information at evening time

  • @mk-or8nm
    @mk-or8nm 2 года назад +1

    Hey Chris, awesome work. Can you show us the DTLS?

  • @jhc4090
    @jhc4090 Месяц назад

    great stuff!

  • @PeterTeehan
    @PeterTeehan 2 года назад

    I see this happen all the time in Direct Routing scenarios. The TLS 1.0 if I recall is actually deprecated and the new protocol is TLS 1.2 or higher. Once the customer updates TLS PSTN calls works. Thanks Chris amazing as always.

    • @ChrisGreer
      @ChrisGreer  2 года назад

      Thanks for the comment Peter!

  • @nic0038
    @nic0038 2 года назад +1

    Excellent

  • @notnull01
    @notnull01 2 года назад +1

    great video, i ran into a similar problem at work, customer was blaming our application it turned out to be a bug in fortigate web filter

    • @ChrisGreer
      @ChrisGreer  2 года назад

      Nice find! These ones are fun to tshoot.

  • @ThePumbaadk
    @ThePumbaadk 2 года назад

    Great, hope more is coming 😀

    • @ChrisGreer
      @ChrisGreer  2 года назад +1

      There is! Always more packets to analyze.

  • @krishangopal4156
    @krishangopal4156 2 года назад

    u r awesome... as alwayz ...
    thanks for sharing this...

  • @AshishKumar-qi5gk
    @AshishKumar-qi5gk 2 года назад +2

    Hey Chris, love your videos. Can you make a video about the tcpdump, tshark etc. I saw your talk on David's channel and you mentioned ring buffers and rotating pcaps. Would be great if you could discuss the same.

    • @ChrisGreer
      @ChrisGreer  2 года назад +1

      ruclips.net/video/DAtyzE1TUlI/видео.html -- got you covered. 🙂

    • @AshishKumar-qi5gk
      @AshishKumar-qi5gk 2 года назад

      @@ChrisGreer Thanks for the prompt response. Do you also have video for tcpdump (with parameters like snap length etc).

    • @ChrisGreer
      @ChrisGreer  2 года назад +1

      @UCIw2fWJDqpn5HsRemCAPOY%F0%9F%91%8DA I don't, not yet... but the ring buffer is demonstrated in that video. I will have to do another one for tcpdump. Thanks for the suggestion.

  • @faran4536
    @faran4536 2 года назад +1

    Nice and short 🔥

    • @ChrisGreer
      @ChrisGreer  2 года назад +1

      Thanks for stopping by Faran!

  • @chrisworthen5403
    @chrisworthen5403 10 месяцев назад

    I have a question. I’m having similar issues but I’m not seeing that handshake start. I see a bunch of TCP traffic but no client hello or sever hello.

  • @beludsden
    @beludsden 2 года назад +1

    Hey Chris, I just stumbled upon your youtube page and wish I had this years ago when I was learning all this stuff, hah! I am currently working on a research project involving TLS and would love to ask you a rather specific question. Would your business email be okay to reach you at? Thank you for everything you're doing here and keep up the amazing quality of videos!

    • @ChrisGreer
      @ChrisGreer  2 года назад +2

      Hey Roy - Sure no problem, you can hit me up on the email in the description. Looking forward to chatting.

  • @CyberNancy
    @CyberNancy 2 года назад

    I’m guessing that a TLS update via the browser on the client is what was needed to fix this problem?
    Just consistently excellent content as usual from Chris.

    • @ChrisGreer
      @ChrisGreer  2 года назад +1

      Thanks for the comment Alan! The vendor had to get into the guts of the api and update it to a modern TLS implementation. Usually by that time I am hands-off (thankfully!)

  • @DJDumlao
    @DJDumlao 2 года назад

    can you do some videos about ssh issues

  • @Black_Swan68761
    @Black_Swan68761 2 года назад +1

    Good work. I noticed when i see your videos i feel like i know everything but when i'm working with Client my head start spinning. I think i need to spend some time to get confidence.
    One i think i can say for sure. Since I've subscribed your channel and trying to keep up with every new video you upload here my knowledge of Wireshark has been increased and all credits goes to you!!!
    Recently i took one your course "Foundational TCP Analysis with Wireshark" at Pluralsight. AMAZING WORK!!!
    Thanks Chris. You are the BEST!!!

    • @ChrisGreer
      @ChrisGreer  2 года назад +2

      I totally understand that - I feel that way too when I am working with my clients sometimes. Just stick to the fundamentals, learn them well. That will always help you!

  • @energy1714
    @energy1714 2 года назад

    Starting form 2:25 you selected 'Version : TLS 1.0', however there is another 'Version : TLS 1.0' below, is there any difference between them? or they are saying the same thing?

    • @ChrisGreer
      @ChrisGreer  2 года назад +1

      Basically they are saying the same thing.

  • @abhaypratap5311
    @abhaypratap5311 2 года назад

    In tls v 1.3 u can't inspect much data using Wireshark

    • @ChrisGreer
      @ChrisGreer  2 года назад

      Past the first two packets of handshake, the conversation is completely encrypted in TLS 1.3. You'd have to decrypt it like I show in other videos on my channel.

  • @sportsboy5935
    @sportsboy5935 2 года назад +1

    who is using tls1.0 its obsoleted ages ago. ?

    • @ChrisGreer
      @ChrisGreer  2 года назад +3

      This was from an IoT device that wasn't connecting properly. Everything I thought I could forget is new again with IoT. 😉

    • @sportsboy5935
      @sportsboy5935 2 года назад

      @@ChrisGreer Agree 👍