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.68k stars 941 forks source link

Uploaded cell information not added to OCID database #608

Open takiainen opened 9 years ago

takiainen commented 9 years ago

Despite uploading several hundred BTS's to the opencellid database, they won't show up at http://opencellid.org/

Android-IMSI-Catcher-Detector keeps claiming that "Cell ID does not exist in OCID database!" despite of downloading new, updated database (several days after succesfully uploading new cellid's). Naturally, this is the result of the cellid's not really ending up in to the database.

My provider is Saunalahti.

EDIT: My device is Oneplus One, running Slimsaber + CAF kernel lollipop ROM (however the issue seems to persist regardless of rom). AIMSICD version is the latest found on fdroid 0.1.34-alpha-b00.

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

TPS commented 9 years ago

@takiainen Just FYI, you're more likely to get a positive response from the dev team when you follow https://github.com/SecUpwN/Android-IMSI-Catcher-Detector/wiki/Submitting-Issues:

:exclamation: SAFETY FIRST: Remove your IMEI, IMSI and phone number from dumps you submit! In all cases, you MUST include the following:

AIMSICD version (see the About-Tab within our App) Your exact FW specification (ROM, AOS API, etc.) Your exact HW specification (processor, model number, etc.) The output of getprop command to a Pastebin-Site (recommended: PIE-Bin) :exclamation: Logcat dump (press button Debugging in Navigation Drawer) Feel free to attach any other logs made by CatLog or Logcat Extreme

which all seems conspicuously absent from your report.…

SecUpwN commented 9 years ago

Hi guys, I'm back! Sorry for letting our project sit for so long. _[Political content removed by E:V:A]_ @takiainen, thanks for filing this. I have noticed that as well and wonder if this is a bug in the OCID system, or if the data is taking a long time to get checked. @msemm, please tell us!

E3V3A commented 9 years ago

I've had this suspicion for a long time, and I think it's because our retrieved dev key data is ignored until we go beta. There is simply too much repeated and possibly bad test data uploaded. Your best bet is to use another app for uploading your cells...

E3V3A commented 9 years ago

See OCID website for apps you can use to upload BTS data.

AFAICR, we had some upload problems with the data CVS formatting used for upload. Or it may have been messed up again after DB overhaul. @ Dev's: we need to look at the uploaded CVS file to see if each column is correct.

SecUpwN commented 9 years ago

I think it's because our retrieved dev key data is ignored until we go beta.

Are you sure? I mean, if a user fetches a fresh key, how can that be ignored?

patrickathompson commented 9 years ago

The issue I am seeing is the same, but the cause doesn't appear to be this codebase. In my scenario, when I double-check the information against Open Cell IDs website, the tower does not show up as found in the database either. I suspect my provider is making rapid and unannounced network infrastructure changes, which the open collective cannot keep up with currently. Unfortunately with an open source application in beta phases, I wouldn't expect this to get better anytime soon. Maybe a better solution would be to allow the user to add cell sites that are known to be TRUSTED as an advanced option or something? That would at least get rid of the nag, prevent alert fatigue, and provide a better user experience.

tbelau666 commented 9 years ago

I wondered about a Toast that said: "Error while uploading..." So I was looking to the log. There is an exception that says "MalformedURLException: Protocol not found". The place in AIMSICD is "...AIMSICD.utils.RequestTask.doInBackground" in line 204. In line 181 is an error that happens before. Seems a Toast can't be initialized. And that happens because the upload data will not be prepared. Anything in AIMSICDDbAdapter.prepareOpenCellUploadData() is going wrong. My version is 0.1.34-alpha-b00 as from F-Droid.

tbelau666 commented 9 years ago

Found: The "OpenCellID/" directory will be created in the preparation of data. The database file(s) will be not. I take a closer look to the sources theese days and will give a pull request. Makes no sense to send the logs when I see the prob by myselfe ;-)

SecUpwN commented 8 years ago

The place in AIMSICD is "...AIMSICD.utils.RequestTask.doInBackground" in line 204. In line 181 is an error that happens before. Seems a Toast can't be initialized. And that happens because the upload data will not be prepared.

Awesome, seems you've found the bug! Thanks for digging so deep, @tbelau666. Please send the pull request when you're ready to and make sure to link this Issue in it so we have the solution at hand. ;-)

tbelau666 commented 8 years ago

Where can I find a list of the external dependencies? I'm trying to import it into Eclipse and... It wil be easier when I could get a list of all needed JARs, their dependencies too and the used versions.

SecUpwN commented 8 years ago

Where can I find a list of the external dependencies?

Not sure what you mean. Have you had a look at Building?

tbelau666 commented 8 years ago

Found. You are using gradle? I have to install it or to find a way to modify the BuildConfig without it. It's auto generated and I didn't see where yet

E3V3A commented 8 years ago

Actually, i think @banjaxbanjo didisabled upload function a while back and we probably forgot to tree enable it...

ghost commented 8 years ago

@E3V3A seems to be working for me and I get upload success message.

Here is the response from server using proxy server to view whats coming in and out of phone.

res

takiainen commented 8 years ago

The problems never was getting the "upload success" message, but instead the fact, that despite the "success", the cell ids never ended into the opencell id database.

He3556 commented 8 years ago

What about saving all CelIDs, the phone was connected to in this area?
And later we can check against our own data. Only when the catcher arrives before the AIMSICD user in that area - than OpenCellID was the only solution. But to upload data to OpenCellID and than download it again for the detection, is not really an improvement.

So what about adding a detection that checks against the internal BTS list?

SecUpwN commented 8 years ago

So what about adding a detection that checks against the internal BTS list?

If this will prevent AIMSICD not detecting the IMSIC when it arrives before the phone moves into the cell, this sounds like a better solution. @DJaeger, what do you think about this? Any better suggestion?