ERROR: Earth.exe has crashed@lemmy.dbzer0.com to Privacy@lemmy.mlEnglish · edit-23 days agoDoes Graphene OS have any implementations of detecting "Unknown Trackers" or does Graphene users just have to risk the possibility of getting tracked by weirdos? (Edit: I mean Bluetooth Trackers)message-squaremessage-square14fedilinkarrow-up138arrow-down11
arrow-up137arrow-down1message-squareDoes Graphene OS have any implementations of detecting "Unknown Trackers" or does Graphene users just have to risk the possibility of getting tracked by weirdos? (Edit: I mean Bluetooth Trackers)ERROR: Earth.exe has crashed@lemmy.dbzer0.com to Privacy@lemmy.mlEnglish · edit-23 days agomessage-square14fedilink
minus-squareERROR: Earth.exe has crashed@lemmy.dbzer0.comOPlinkfedilinkEnglisharrow-up3·3 days agoSo its a dilemma. Either turn on bluetooth so you can detect trackers, but you then expose your bluetooth MAC address allowing others to track you. Or turn off bluetooth, but you’ll never know if there’s a secret track on you. Wonder if there’s a way to passively scan for trackers without emitting bluetooth signals. (Does Graphene OS allow MAC address randomization for bluetooth?)
minus-squarejet@hackertalks.comlinkfedilinkEnglisharrow-up6·edit-23 days ago Does Graphene OS allow MAC address randomization for bluetooth Actually, I believe AOSP allows for a MAC address randomization when not connected to a device, but as the UCSD paper above indicates, it’s still quite fingerprintable
So its a dilemma.
Either turn on bluetooth so you can detect trackers, but you then expose your bluetooth MAC address allowing others to track you.
Or turn off bluetooth, but you’ll never know if there’s a secret track on you.
Wonder if there’s a way to passively scan for trackers without emitting bluetooth signals.
(Does Graphene OS allow MAC address randomization for bluetooth?)
Actually, I believe AOSP allows for a MAC address randomization when not connected to a device, but as the UCSD paper above indicates, it’s still quite fingerprintable