You just intercept the traffic after its decrypted on the server side, or are you suggesting you somehow send encrypted traffic that never gets decrypted?
It's just not technically feasible, so there's nothing to lie about. They're not MITMing petabytes/sec across dozens (hundreds?) of companies and they haven't broken TLS1.3.
If I have a box at Digital Ocean and I'm communicating with it with TLS1.3 using a Let's Encrypt cert that I generated, where, exactly, does this magical MITM box come into play?
Of course it's feasible, you just intercept the traffic post-decryption on the cloud/server side. You don't control how/where your traffic to 3p cloud services is decrypted.
> This was their third office space, serving as their headquarters before they outgrew it and eventually relocated to Market Square at 1355 Market Street in 2012. The arab spring twitter uprising was fully a CIA/NSA operation.
To be clear, the claim you're making is that because Twitter has their third corporate office in the same building as an AT&T switching center, and US intelligence used a room in AT&T's switching center for surveillance, then Twitter must have been controlled by US intelligence? And thus the Arab Spring uprising, where Twitter was used, was "fully a CIA/NSA operation"?
Yes, twitter was used by US 3 letter agencies to assist in the arab spring. To be able to do it in a surreptitious way they were asked to move to that building and get access to all private DMs, and for doing so they got a fat tax break to move to "blighted" market street current location. All of those things fit the timeline and snowden capability disclosures.
Yes, you have collected a lot of random bits of information from over a decade ago. I'm sure everything you say is still relevant today, especially the conspiracy nonsense.
Some of us actually work in security, while others think the NSA and CIA are some magically powerful orgs.
Explain how, even with the mystical Room 641A, the NSA can't break a TLS1.3 protected communication channel without either party knowing about it. Assume you have generated a cert with Let's Encrypt. How, exactly, does that work?
Explain to me how you are going to encrypt your LLM API calls with your let's encrypt cert.
There are also multiple ways/places traffic you send to typical cloud/tech company is decrypted and can be intercepted. (Surprised I have to point this out to someone who 'actually works in security ' lol)
Not to mention US tech companies fully cooperate with the NSA in many cases and are aware of this going on.
why is europe going to such great lengths to build datacenters and ensure they have no connection to US jurisdiction... GDPR means nothing if there is a persistent threat installed on every instance.
you compel the host under similar threat of non-existance to grant you view of the hypervisor. you're not running on bare metal with alternate TPM's that arent the Intel IMU (also backdoor'd) so you're just as pwnable.
now say you're doing this on a raspberry pi or other openhardware like a librum machine with a yubikey hsm on local wifi or physical ethernet... you may have a shot at the privacy you're looking for.
https://en.wikipedia.org/wiki/Room_641A
Yeah, they did (and probably do).