-
-
Notifications
You must be signed in to change notification settings - Fork 221
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ring Airtags #269
Comments
Duplicate of #226. |
Wait, that's not the same? |
I mean ringing Airtags with the Flipper, not ringing the Flipper like an Airtag in Apple's App. |
What is the point of this? Airtags are not paired to the flipper |
Might be interesting to see how the app does it though, considering they aren't paired to the android devices either... if it's a Bluetooth signal it may be possible |
They Send a Signal specifically for the point to be detected and ringed. |
"Bluetooth signal" "send a signal" it's not that easy. If it requires the master device starting a connection to the airtag, you can kiss goodbye to this on flipper. If it is an advertisement packet, it could work. But what do you put in the packet? Obviously there is no packet that makes ALL airtags ring, that would be stupid and Apple is many things but not stupid. Most likely, there's a packet that tells the airtag to ring, and it contains an identifier for what airtag should ring, so only that one rings. How do you find this identifier? A phone can scan nearby devices. Flipper cannot. And you sure as hell are not typing 64+ hexadecimal characters to identify the airtag. |
"But bRuTeFoRcE!!" Bruteforcing this will take 8(possible values for a byte) ^ 32(rough estimate, public keys used by airtags are even longer than 32 bytes since they use both the 31 byte adv payload and the 6 byte MAC address, but let's keep it on a lower estimate) which gives 7,922816251426e28 possible identifiers, assuming 20ms advertising rate this means 5,024617105166e19 YEARS for bruteforcing airtags. |
Ok, sorry, I didn't know the Flipper couldn't scan... |
Yeah, another sad limitation of having the light ble stack |
But the the Flipper should be able to send specific Bluetooth packets, if so, you could make an app like BLE spam where you enter the entire hex code, and not just the model code which is then put in the hex code that is beeing send. If you can edit or type the hex code yourself, you should also be able to set the TX Power (signal strength) that the Flipper tells the other ble devices like your phone. Just a thought of me, because while sniffing the ble package that the Flipper sends, the byte after 0a was randomized for every signal. jb0x168.github.io/ble-spam-analysis says: "There are several AD Types. Most of them, like Flags (0x01) and TX Power (0x0a) are standard types that are used by both Google and Apple protocols." |
I think I know what you mean. There is a custom Bluetooth advertisement application on backlog for mntm that perhaps could be used for this purpose but something tells me this isn't advertisement packets we are talking about. It would require sniffing the Bluetooth signal from a different device and then manually entering the hex code on the flipper. In hindsight it's not really worth it. Imagine going through all that effort just to be able to make one AirTag make a noise. Unless it was possible and a Bluetooth packet playlist was implemented and those codes don't rollover (because the AirTag advertisement data does). |
I meant a Hex code BLE Spam/Sender in general, not just for this purpose. The example from me above is meant like the BLE spam app but you can edit the entire hex, not just the model code that the app then puts into the hex with other hex code. Because then you can edit the TX Power (signal strength (not sending signal stronger, but saying with how much power the signal is sent, so that the other device knows the range of the Device that send the signal.)) or stuff other in the Hex. |
Ah yeah. Again, in backlog. "BLE Spoof" app, custom advertisement data and what not. Once that's made then yes that should be possible. Have a look at the projects menu and it'll be in the firmware progress tracker. |
An app for Android that can do what I mentioned is nRF Connect. It has a few more tools in its arsenal and is a bit more organized when entering hex because it puts it in automatically, so you don't type out the raw hex. That's why it is also good for beginners in BLE. |
Description of the feature you're suggesting.
DarkFlippers/unleashed-firmware#625
I can do it in my Android Settings, so should be possible, right?
Anything else?
no
The text was updated successfully, but these errors were encountered: