> Read rf signal and emulate it or save it
I assume it checks that you actually have the licensing requirements to be transmitting on whatever frequency?
replies(1):
I assume it checks that you actually have the licensing requirements to be transmitting on whatever frequency?
That article you shared seems to say the problem is bigger than the used hardware even:
> Soon after, developer Simon Dankelmann ported the attack to an Android app, allowing people to launch Bluetooth spam attacks without needing a Flipper Zero.
How do you solve that without outlawing Android devices?
> People using Bluetooth-enabled hearing aids and heart rate monitoring tools also reported disruption, which could put their well-being at risk.
This is probably the most bananas part of that article, and it's great that they managed to find these issues in relatively trivial conditions, since the company's own testing apparently doesn't include very basic security checks. If those devices are failing when they aren't connected to the main device, what makes these companies even remotely suitable for building critical devices like that?
Who knows how long time it would take to discover these security issues with medical devices if people weren't able to prototype these sort of attacks at home?
And that happens in lots of other cases too, when it's too far away, out of battery, damaged, does that mean their vital health devices stop working if that's happening? Sounds like they need to work on reliability if that was true.