• Akip@discuss.tchncs.de
    link
    fedilink
    arrow-up
    0
    ·
    edit-2
    5 months ago

    Thanks for clearing up my WiFi mix-up. From my understanding the same attack path still applies even to https://grapheneos.org/features#lte-only-mode and respectively https://grapheneos.org/usage#lte-only-mode correct?

    https://en.wikipedia.org/wiki/International_Mobile_Subscriber_Identity states the phone would send a https://en.wikipedia.org/wiki/Mobility_management#TMSI most of the time? But your point about the IMEI still stands. So there is no real way to protect yourself other than to turn off cell tower roaming?

    • electric_nan@lemmy.ml
      link
      fedilink
      arrow-up
      0
      ·
      5 months ago

      Thanks for the links. There’s some new information in there that I’ll have to look further into. For one, I’ve never heard of security concerns about 5G versus 4G.

      I also wasn’t aware of the TMSI at all. I still don’t fully understand some things about it which would be important considerations:

      How is this randomized number assigned/correlated to the IMSI? Is it done by the tower?

      It seems like the carrier can request the actual IMSI at any time. Can these CSS also do that? TMSI is supposed to protect against ‘eavesdroppers’ but these industrial a grade CSS might have greater capabilities than passive eavesdropping.

      I am unsure if or how disabling roaming would protect you from CSS. For one, the spoofing might make your device think it isn’t roaming. Secondly, the CSS might still be aware of your device anyway, even if it doesn’t establish an open connection to it. The phone and the tower need some minimum communication to even determine if you’re roaming or not.