A team of university researchers has devised a new side-channel attack named 'Freaky Leaky SMS,' which relies on the timing of SMS delivery reports to deduce a recipient's location.
A team of university researchers has devised a new side-channel attack named ‘Freaky Leaky SMS,’ which relies on the timing of SMS delivery reports to deduce a recipient’s location.
It seems like it would be pretty easy to mitigate on the OS level by adding a random delay to delivered receipts without any meaningful inconvenience to end users. A few seconds here or there isn’t going to make or break anything experience wise.
Or does that less than instantaneous response result in a bunch of extra traffic trying to redeliver messages?
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !technology@beehaw.org
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
Interesting approach.
It seems like it would be pretty easy to mitigate on the OS level by adding a random delay to delivered receipts without any meaningful inconvenience to end users. A few seconds here or there isn’t going to make or break anything experience wise.
Or does that less than instantaneous response result in a bunch of extra traffic trying to redeliver messages?