- cross-posted to:
- protonprivacy@lemmy.world
- cross-posted to:
- protonprivacy@lemmy.world
No answer yet from what I’ve seen. Possibly Mess up from an unreviewed vibe coded mess. Or worse yet , intentional.
No answer yet from what I’ve seen. Possibly Mess up from an unreviewed vibe coded mess. Or worse yet , intentional.
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.
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.
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/
I see, thanks. Til