search

CellularPrivacy / Android-IMSI-Catcher-Detector

AIMSICD • Fight IMSI-Catcher, StingRay and silent SMS!
https://cellularprivacy.github.io/Android-IMSI-Catcher-Detector/
GNU General Public License v3.0
4.73k stars 946 forks source link

New priorities and ToDos (re-orientation) #628

Open He3556 opened 9 years ago

He3556 commented 9 years ago

Priorities (fight against the chaos of issues - here is a short & clear list what we should be doing...)

... for the old parts of the project: 1. Fix wrong "changing LAC" alerts (i have an idea how to fix it - let me know if you want to help) 2. Add the detection "Check BTS for the NC List "[https://github.com/SecUpwN/Android-IMSI-Catcher-Detector/issues/264] 3. Check Cell-IDs against table "unique BTS". We use the same logic like the check against OpenCellID db. We need to add a "learning mode" - after 24h of exploration the system checks if there are new CellIDs. (i will open a issue for that when the time is right)

... new parts: 4. connect a RTL-SDR (USB) to the Android phone to receive extra values for detection. There are projects out there "how to sniff on GSM..." to listen to other peoples conversations. But we can use it to monitor our own connection (BCCH of CellTowers and many more) (i will open a issue soon)

5. Ensuring compatibility: Besides (Issue #269 ) We should build a list with phone models that:

  1. Can provide information about NCL
  2. Detecting true/false changing LAC alarms
  3. Show Silent SMS That would be helpful for the future and interesting for our users.

I will start with no.4 asap. (january) If anybody has experiences how we can get the values out of the decoded stream and put it into a database, please let us know!

Somebody want to work on any number? Please let me know and i will work out the details...

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

marvinmarnold commented 9 years ago

Priorities (fight against the chaos of issues - here is a short & clear list what we should be doing...)

Great ideas @He3556. Can I recommend that we also add 5. Ensuring compatibility?

  1. Fix wrong "changing LAC" alerts (i have an idea how to fix it - let me know if you want to help)

I want to help with #1, is there an open ticket?

He3556 commented 9 years ago

No sorry, not right now. But i will open one (for no.1) in the next 2 days.

And yes, i will add 5. Ensuring compatibility to the list and I will add this informations (of this issues) into the wiki. And we can still discuss it here

SecUpwN commented 8 years ago

Thanks for stepping foward, @He3556. It is wonderful to have your heartblood with us, our project has gotten way too messy and me leaving for so long did not contribute to a better state either. @marvinmarnold, I have seen that you're now running your own app from our base code - are you still interested in a merge, or do I have to calm down my mind now that you're now doing "your own thing"? :P

marvinmarnold commented 8 years ago

Hey @SecUpwN, I thought I was clear from the beginning about having forked AIMSICD to give it a more user friendly UI. I'm still very interested in finding ways to merge my work back into AIMSICD.

That said, work on my fork has slowed down a lot since I realized that core AIMSICD functionality is actually quite limited. #1 and my suggested #5 have combined to make AIMSICD pretty inoperable on most phones I have tried.

Anyways, I'm still happy to see how AIMSICD grows and hope I can find the time to contribute.

agilob commented 8 years ago

@marvinmarnold do you have a screenshot?

He3556 commented 8 years ago

@marvinmarnold thx for helping on No1. of the list.

The characteristic of a true "changing LAC" alert is, that the LAC value of one certain cell is changing once or maybe a few times in short intervals (1-10 minutes). But it makes no sense to raise the alarm when the LAC of many Cells are changing over the day. And that is what happens if the phone can't read the correct LAC or has timing problems in general. So we need to filter these (yellow) alarm if this conditions are true.

1.1. Maybe add a value "false changing LAC alarms present = True/False", to decide if the yellow alarm will really be shown on the display. We can discuss how this can be implemented. (EventLog, i would leave it like it is, so we have the data of false alarm for research...)

Next problem will be - after the App is installed, it will still show the (false) yellow alarm until it detects more ch. LACs in other CellIDs and will switch to "false ch... = True"

1.2. We start with "false changing LAC alarms present = True" as default. After 24hour "exploration time" and if there were no false alarms, we switch to "False"

SecUpwN commented 8 years ago

@He3556, here is an interesting read for your point 4: Cracking and sniffing GSM with a RTL-SDR.