• I Cast Fist@programming.dev
    link
    fedilink
    English
    arrow-up
    4
    ·
    8 hours ago

    Packet data has headers that can identify where it’s coming from and where it’s going to. The contents of the packet can be securely encrypted, but destination is not. So long as you know which IPs Signal’s servers use (which is public information), it’s trivial to know when a device is sending/receiving messages with Signal.

    This is also why something like Tor manages to circumvent packet sniffing, it’s impossible to know the actual destination because that’s part of the encrypted payload that a different node will decrypt and forward.

    • Ulrich@feddit.org
      link
      fedilink
      English
      arrow-up
      1
      arrow-down
      1
      ·
      edit-2
      3 hours ago

      Packet data has headers that can identify where it’s coming from and where it’s going to

      Wouldn’t you have to have some sort of MITM to be able to inspect that traffic?

      This is also why something like Tor manages to circumvent packet sniffing

      TOR is what their already-existing tip tool uses.

      • Cenzorrll@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        3 hours ago

        Wouldn’t you have to have some sort of MITM to be able to inspect that traffic?

        You mean like your workplace wifi that you’re blowing the whistle at?