• Godort@lemmy.ca
    link
    fedilink
    English
    arrow-up
    79
    arrow-down
    3
    ·
    1 day ago

    This is probably fine. The connection to DDG will be over HTTPS, so a captured packet would need to be decoded first. And if someone were to manage to break the encryption, then they would also need to know what service you used the password for.

    Ultimately, it’s more secure to generate locally, but it would be a huge amount of work to get anything usable out of a packet capture

    • warm@kbin.earth
      link
      fedilink
      arrow-up
      19
      arrow-down
      1
      ·
      1 day ago

      Are they sending data? I’m pretty sure this will just be generated on the client.

    • TehBamski@lemmy.world
      link
      fedilink
      English
      arrow-up
      8
      arrow-down
      2
      ·
      edit-2
      1 day ago

      I’m no cybersecurity expert. But couldn’t they just sniff your traffic to see where you (your packets) go and test the pw on each login for the last hour?

      edit: I guess they are using DuckDuckGo, which has a higher level of privacy design and limits.

        • nef@slrpnk.net
          link
          fedilink
          English
          arrow-up
          1
          ·
          12 hours ago

          DoH is good, but it wouldn’t help much in this scenario. Even if every website you connected to supported Encrypted Client Hello, IP addresses greatly narrow down which domains you’re connecting to.

          But realistically using DDG to generate a password is safer than downloading a local program to do it, an attacker would have to break into DDG and MITM your internet. For a local program all they have to do is compromise the site you download it from, and maybe the developer’s signing key if you check that.