• 55 Posts
  • 2.95K Comments
Joined 2 years ago
cake
Cake day: October 23rd, 2024

help-circle
  • bombs hitting a house do create emissions from bomb and any burning matter. Oil on fire, absolutely creates emissions comparable to their refined products, and also needs replacement oil to meet original demand for products. Investments in new oil drilling or refineries to meet any current scarcity will also be sucked up until they are dry, or keep producing even if most of the world prefers clean energy. Their production/transportation is some emissions too.

    OP is calculating end user consumption for fuels. I’m not sure OP gave an exact number, but they are saying you will drive F150 3-5% less on average.










  • How a “Backdoor” in HTTPS Can Occur

    Because HTTPS relies on the Transport Layer Security (TLS) protocol to encrypt data, any backdoor must target the underlying cryptography, implementation, or trust infrastructure:

    • Weakened Cryptographic Standards: The US National Security Agency (NSA) has a documented history of attempting to introduce subtle flaws into global encryption standards. A prime historical example is the Dual_EC_DRBG random number generator. The NSA pushed for its inclusion in NIST standards in the mid-2000s, which later revealed a mathematical backdoor allowing anyone with the correct key to decrypt the resulting traffic.

    • Compromised Certificate Authorities (CAs): HTTPS relies on a chain of trust managed by Certificate Authorities. These entities issue the digital certificates that verify a website’s identity. If a US-based CA were legally coerced (via classified directives like National Security Letters) to hand over its root keys or issue fraudulent certificates, an agency could execute a Man-in-the-Middle (MitM) attack to decrypt HTTPS traffic seamlessly.

    • Imposed Implementation Flaws:

      Backdoors are often engineered directly into commercial hardware or software rather than the open-source protocol. Government agencies can exploit or intentionally plant vulnerabilities in proprietary routers, firewalls, and operating systems that handle HTTPS termination, allowing them to capture data right before it is encrypted or after it is decrypted.

    • Key Interception (PRISM): Revelations from 2013 leaked documents showed that under programs like PRISM, the US government bypassed the need to break HTTPS encryption entirely by compelling major tech companies to hand over data directly from their servers (at rest), rendering transit encryption irrelevant.