• shortwavesurfer@lemmy.zip
    link
    fedilink
    arrow-up
    15
    arrow-down
    2
    ·
    edit-2
    11 days ago

    As far as Let’s Encrypt goes, the easy way to solve that is self-signed SSL certificates and Tofu. Just make it stupid obvious if an SSL certificate changes on a site that you go to. Like, turn your browser into a giant red screen that says that the security of the website has changed and may be broken obvious. Maybe you could have search engines also index SSL certificates so you could see if Google and Bing and DuckDuckGo and whoever else all say that this website has the same SSL certificate that it has had for X amount of time and if the search engines start showing different results you get suspicious.

    Edit: Using self-signed certificates and tofu fits better with the decentralized ethos of the original web anyway since you’re not relying on some third-party authority to tell you what’s safe and what’s not.

    • WhyJiffie@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      3
      ·
      10 days ago

      i don’t think this is a good idea. govs could just set up a big reverse proxy for lots of sites to serve them with their own certs, and you wouldn’t know

      • shortwavesurfer@lemmy.zip
        link
        fedilink
        arrow-up
        2
        ·
        10 days ago

        Seems like no change from right now, because currently the certificate authorities are centralized entities, which could be pressured by governments to add their own certificates.

    • Petter1@lemm.ee
      link
      fedilink
      arrow-up
      2
      ·
      10 days ago

      How about a Blockchain or Directed Acyclic Graph (DAG) out of SSL certs 🤔

      I think that would finally be a use case for that tech, lol

        • Petter1@lemm.ee
          link
          fedilink
          arrow-up
          1
          ·
          9 days ago

          If you issue a certificate, you proof ownership via * challenge–response test that is validated by each node. If x% (like eg. 70%) of nodes agree that the test is passed, the block counts as validated and can be placed onto the chain. (Each node places the block on their chain and the hash must be same as hash of chain of majority of nodes)