Wireshark class 4.3 - How to analyze a packet capture Certificates & TLS Encryption Troubleshooting

แชร์
ฝัง
  • เผยแพร่เมื่อ 27 ม.ค. 2025

ความคิดเห็น • 9

  • @LanWanNinja
    @LanWanNinja  10 หลายเดือนก่อน

    Powershell commands used:
    md /temp
    cd /temp
    Certutil.exe -generateSSTFromWU roots.sst
    $sstStore = ( Get-ChildItem -Path c:\temp
    oots.sst )
    $sstStore | Import-Certificate -CertStoreLocation Cert:\LocalMachine\Root

  • @stevekayak
    @stevekayak 10 หลายเดือนก่อน +2

    Nice tutorial. Thats a handy command to update the root certs. My certs went from 52 to 485 !

    • @LanWanNinja
      @LanWanNinja  10 หลายเดือนก่อน

      That's great to hear! And thanks.

  • @robguitar7
    @robguitar7 9 หลายเดือนก่อน +2

    Wow! Very informative. I've seen a bunch of vides but not as detailed and easy to understand as yours. I will be referencing these from here on out. Thanks for videos!

    • @LanWanNinja
      @LanWanNinja  9 หลายเดือนก่อน

      Thanks so much! I appreciate it!

  • @Finito54ify
    @Finito54ify 10 หลายเดือนก่อน +1

    Very informative and well structured video!
    Good explanations on how to use wireshark - tinkered around a bit, but never got, what I was looking for
    I went from 68 certs to 490 :D

    • @LanWanNinja
      @LanWanNinja  10 หลายเดือนก่อน +1

      Thank you!! And great to hear on the cert numbers!

  • @rudypieplenbosch6752
    @rudypieplenbosch6752 10 หลายเดือนก่อน +1

    Wow that is some analyses you do there. I will use wireshark as well, having sime weird issues with Pfsense, one virtualized and a normal pfsense, they both work great separately, only the virtualized one, doesn't let me write things to my server, or it writes something but very slow. Reading goes blisteringly fast a very weird issue, i can ping everything fine, in both cases the same vlans are used, anyway i will find it with wireshark.

    • @LanWanNinja
      @LanWanNinja  10 หลายเดือนก่อน

      Thanks!! Yeah, I can't tell you how many times I have looked at an issue and thought one thing and then the packets said something else. That sounds like that kind of issue.