I kinda don’t trust my home network because my brother is douche and I feel like he’s gonna do some weird things with the connection, so I prefer to juse use my phone’s data (unlimited data plan) to avoid any shenanigans. Hypothetically, how much harm can an evil wifi do?

Does using HTTPS avoid all risks? What about evey program on your computer or every app on your phone, do they also have HTTPS everywhere on? (I use Android btw)

How much could a VPN do better that HTTPS cant?

  • hemko@lemmy.dbzer0.com
    link
    fedilink
    English
    arrow-up
    18
    ·
    2 months ago

    As others have mentioned, DNS is probably your worst enemy. It doesn’t take much technical knowledge to just create a DNS server and start logging all domains you’re accessing. Say, to tell mom how often you’re browsing porn or something.

    Manually configuring DNS servers in your OS would resolve this issue, but also using VPN like mullivad would just bypass such worries with 99% certainty.

    Or just keep using mobile data, because why not

    • Peffse@lemmy.world
      link
      fedilink
      arrow-up
      7
      ·
      2 months ago

      Correct me if I’m wrong but- manually configuring your DNS in the OS would still enable traffic monitoring, wouldn’t it? I always thought DNS traffic is not encrypted by default.

      • hemko@lemmy.dbzer0.com
        link
        fedilink
        English
        arrow-up
        3
        ·
        2 months ago

        Oh, yeah you’re absolutely correct. I was fixated too much on the DNS logging lol

        DoH (DNS over HTTPS) or DoT (DNS over TLS) would fix that

        • ShortN0te@lemmy.ml
          link
          fedilink
          arrow-up
          4
          ·
          2 months ago

          Actually no. The SNI is still not encrypted. So every site you are visiting can still be sniffed.

          • Akui@lemmy.ml
            link
            fedilink
            arrow-up
            3
            ·
            edit-2
            2 months ago

            This is resolved in TLS 1.3 with ECH. Adoption is still not wide though, so your concern is valid.

            • ShortN0te@lemmy.ml
              link
              fedilink
              arrow-up
              2
              ·
              2 months ago

              Was not aware ECH was actually in TLS 1.3 thanks for that. But yes it will take a long time for widespread adoption.

      • pHr34kY@lemmy.world
        link
        fedilink
        arrow-up
        2
        ·
        2 months ago

        I’ve configured my home wifi to capture all DNS regardless of its intended recipient. It’s unencrypted so it’s possible.

        I also use encrypted DNS on my phone.

  • doodledup@lemmy.world
    link
    fedilink
    arrow-up
    3
    ·
    edit-2
    2 months ago

    Https only encrypts the packet content.

    What can happen:

    TL;DR: Evesdropping, spoofing, device vulnerabilities (e.g. using exposed ports).

    • Attackers can listen and log to which servers you’re talking to. This can be combined with the attack explained in the following.
    • The can do spoofing attacks by replying to your DNS request with their own IP. For example: you open domain.com and the attacker will not forward domain.com to the trusted DNS server but will instead send you their own IP and website that looks exactly like the website you intent to visit. Since they control this spoofed website they can also intercept all the credentials you enter. If you don’t enter credentials or upload or download stuff, nothing can happen. However you’ll be safe from spoofing attacks in most cases as popular websites use HSTS which hardcodes the IP addresses corresponding to domains result into your browser, bypassing DNS.
    • An attacker could exploit device vulnerabilities that are unrelated to https web traffic. So make sure your OS and software are up to date and you don’t have applications running with exposed ports!

    A VPN will prevent the first two attacks.