Cool, an IMSI Catcher Catcher. I am reminded of the otherwise unremarkable 1998 action comedy "The Big Hit."
Not only does this trace buster keep a buster from tracing your call, but it can also trace the MF that's tracing your shit. But if them MFs got a trace buster too, that's why I gots this trace buster BUSTER. See when a MF try to bust your trace with a trace buster, this MF gonna bust the MF trace buster that's busting your trace.
If you make a Rayhunter, think twice before enabling its smartphone notification feature. The documentation doesn't directly warn, but presumably the notifications leak the fact that you use Rayhunter, and they go through centralized services. (With notifications being practically easier for some parties to check centrally, than how the device appears to the various cellular network towers.)
As situations sometimes become complicated in a locale, I suppose that this leaking could get you flagged as a potential troublemaker, or included in a small pool of persons of interest regarding an event/incident, etc.
(Most people neither think about nor are concerned with such possibilities, but if you find this device fun or interesting, then I'd guess probably you are more likely than the average person to want to reconcile how it works, with your fun/interesting/real threat model.)
Not that I imagine most people would change it, but notably ntfy means that notifications don't have to go through centralized services. (As you can set what ntfy URL you want to use, including to your own server)
I guess if you set up an `ntfy` server, and you also run the `ntfy` app on iOS, then the `ntfy` app can do a local notification on the iOS device (without going through Apple APN servers)?
Then it looks like you can probably just do the communication between server and app using HTTP(S), though the app either needs to keep a connection open or poll frequently (with entirely new TCP and possibly TLS connection negotiation each poll time):
`ntfy` is impressive, but there's a lot of implementation to it that could have vulns, there's substantial server config to do, the app-side UX polish isn't great, and the connection method is inefficient. But it might not obviously leak to some centralized thing outside your control (unlike if you do iOS push notifications the normal way).
> To protect yourself from Cellebrite you can use a strong password, turn off biometric unlocks, and keep your phone up to date.
To add, if you truly want to prevent any forensics on your iPhone (especially if you are traveling), make sure to pair lock your iPhone to a MacBook you leave in your house.
When they say the recommended hotspot device used for this is cheap, they really are.
The recommended device for the Americas is US$11 (refurbished) on eBay with free US shipping. US$14 for shipping to Canada :(
https://www.ebay.com/itm/276624956523
and brand new units for US$20
There’s another seller with 50 for US$160
Cool, an IMSI Catcher Catcher. I am reminded of the otherwise unremarkable 1998 action comedy "The Big Hit."
Not only does this trace buster keep a buster from tracing your call, but it can also trace the MF that's tracing your shit. But if them MFs got a trace buster too, that's why I gots this trace buster BUSTER. See when a MF try to bust your trace with a trace buster, this MF gonna bust the MF trace buster that's busting your trace.
https://www.youtube.com/watch?v=2VY_xxL2jL0
If you make a Rayhunter, think twice before enabling its smartphone notification feature. The documentation doesn't directly warn, but presumably the notifications leak the fact that you use Rayhunter, and they go through centralized services. (With notifications being practically easier for some parties to check centrally, than how the device appears to the various cellular network towers.)
As situations sometimes become complicated in a locale, I suppose that this leaking could get you flagged as a potential troublemaker, or included in a small pool of persons of interest regarding an event/incident, etc.
(Most people neither think about nor are concerned with such possibilities, but if you find this device fun or interesting, then I'd guess probably you are more likely than the average person to want to reconcile how it works, with your fun/interesting/real threat model.)
Per <https://efforg.github.io/rayhunter/configuration.html>:
> ntfy URL for Sending Notifications, which allows setting a ntfy URL to which notifications of new detections will be sent. The topic should be unique to your device, e.g., https://ntfy.sh/rayhunter_notifications_ba9di7ie or https://myserver.example.com/rayhunter_notifications_ba9di7i.... The ntfy Android and iOS apps can then be used to receive notifications. More information can be found in the ntfy docs.
Not that I imagine most people would change it, but notably ntfy means that notifications don't have to go through centralized services. (As you can set what ntfy URL you want to use, including to your own server)
I guess if you set up an `ntfy` server, and you also run the `ntfy` app on iOS, then the `ntfy` app can do a local notification on the iOS device (without going through Apple APN servers)?
Then it looks like you can probably just do the communication between server and app using HTTP(S), though the app either needs to keep a connection open or poll frequently (with entirely new TCP and possibly TLS connection negotiation each poll time):
https://docs.ntfy.sh/config/
https://docs.ntfy.sh/publish/
`ntfy` is impressive, but there's a lot of implementation to it that could have vulns, there's substantial server config to do, the app-side UX polish isn't great, and the connection method is inefficient. But it might not obviously leak to some centralized thing outside your control (unlike if you do iOS push notifications the normal way).
The ntfy maintainer is here on HN if you want to send ideas:
https://news.ycombinator.com/user?id=binwiederhier
I wonder if there's a usb option to get a notification on your PC?
But someone else did: https://san.com/cc/exclusive-evidence-of-cell-phone-surveill...
using a different tool, "Marlin". The article has some technical details.
This is such a neat and fun project! I saw these flying off the shelf at Def Con.
> To protect yourself from Cellebrite you can use a strong password, turn off biometric unlocks, and keep your phone up to date.
To add, if you truly want to prevent any forensics on your iPhone (especially if you are traveling), make sure to pair lock your iPhone to a MacBook you leave in your house.
https://arkadiyt.com/2019/10/07/pair-locking-your-iphone-wit...
Since the protest hypothesis hasn’t proven accurate, are there alternatives?
We should patch the firmware to be like purpleair.com and have a map with this kinda activity.
Any idea how you would abuse control a project like that if it's no cost for the hardware?
Nice
[dead]