No answer yet from what I’ve seen. Possibly Mess up from an unreviewed vibe coded mess. Or worse yet , intentional.

  • Awesome Lowlander@cozyver.se
    link
    fedilink
    English
    arrow-up
    1
    ·
    3 hours ago

    I don’t get it. The whole point of encryption is that only the recipient can decrypt it, regardless of what role you play in the middle. Unless you’re reading it before the encryption happens.

    Not saying it’s bullshit, just not jiving with my very basic understanding of this.

    • assaultpotato@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      1
      ·
      edit-2
      3 hours ago

      For MITM attacks you need to own the network you’re on and then you have the client connect to you with a cert the client will trust (by adding to the client’s trusted cert bundles or or or) and then sniff as you proxy upstream to the real intended host.

      This is why people say not to trust random WiFi networks.

    • assaultpotato@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      1
      ·
      3 hours ago

      For option 1, since you are the device, you just need to use the TLS certificate from the session, which you can capture otherwise. This is just the first source I could find: https://support.atlassian.com/atlassian-knowledge-base/kb/how-to-capture-http-traffic-using-wireshark-fiddler-or-tcpdump/

      Decrypt with SSLKEYLOGFILE

      Wireshark has the ability to use SSLKEYLOGFILE to decrypt https traffic. This file is a feature provided by the web browser. When a Web Browser is configured to create and use this file all of the encryption keys created for that session are logged. This allows Wireshark to decrypt the traffic. If you supply SSLKEYLOGFILE and a pcap file that were taken at the same time, wireshark will show you all of the web traffic.