Technology

37724 readers

768 users here now

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.

Subcommunities on Beehaw:

This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 2 years ago

MODERATORS

alyaza@beehaw.org

TheRtRevKaiser@beehaw.org

gyrfalcon@beehaw.org

rs5th@beehaw.org

Los@beehaw.org

coldredlight@beehaw.org

SemioticStandard@beehaw.org

TheRtRevKaiser@kbin.social

remington@beehaw.org

SMS delivery reports can be used to infer recipient's location (www.bleepingcomputer.com)

submitted 1 year ago by cavemeat@beehaw.org to c/technology@beehaw.org

2 comments fedilink hide all child comments

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.

you are viewing a single comment's thread
view the rest of the comments

[–] conciselyverbose@kbin.social 9 points 1 year ago

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?