Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • A Android-IMSI-Catcher-Detector
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 162
    • Issues 162
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 5
    • Merge requests 5
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • CellularPrivacy
  • Android-IMSI-Catcher-Detector
  • Issues
  • #926
Closed
Open
Issue created Apr 09, 2017 by Administrator@rootContributor

README! The future and continued survival of AIMSICD

Created by: E3V3A

It has come to my attention that apparently AIMSICD has become even more popular the less it works.

I will say the following not out of disrespect for the many contributors and all the hard labor put into this app, to try to make it work, but as an honest recommendation to all developers here, still thinking this will happen. As it stands right now, it simply will not! And it hasn't worked for the last 2 years (when I left the project), and probably never will unless there is a radical change in matters.

It seem that no one at the CellularPrivacy organization is able to maintain this? SecUpwN lost his account? OpenCID is closing down. The DB is totally broken and useless from all development aspects. The app is bloated with eye-candy, obscure and useless functions and libraries. The translation integration is bloating the commit history to the point its impossible to follow any valuable coding whatsoever.

However, due to recent world political changes and the extremely easy access to SDR home-brew IMSI catchers and constant 2FA hacks using mobile network MiTM techniques. This app is indeed still needed, especially for a wider hardware spectrum. So I am reconsidering to revive my interest in this development effort. BUT

Thus, IFF (If and only if) I am to venture into the revival of this app, it will have to be under the following conditions.

  • The app development will be under a new organization that I am in control of.
  • The app specifications will be strictly held to and hawk-eyed according to my specifications
  • The app detections will be strictly held to and hawk-eyed according to my specifications
  • The app will not have any automatic translations. It will be English only, until the day it's finished. (So no need to worry about RTL, i18 and all that junk.) It should be bloody well simple enough UX that any language should not be necessary.
  • The app will have a bare-bone, ultra minimalistic structure and UI. (No star-wars themes, etc.)
  • The app will again use well known and great SQLite3 DB as originally specified but reduced to need.
  • The detection's will be updated and modularized.
  • The detection should be primarily instantaneous and secondarily retrospective. (I.e. Use obvious detection's first and deeper SQL analysis second.)
  • Minimum API support should be API 21, Lollipop. (If you are really concerned about security and still using AOS less that Marshmallow, you're really not that interested!) I can't be bothered with having to deal with obsolete and outdated API issues and legacy code.
  • Java 8
  • External library free to the greatest extent possible. (Do we really need that 1 MB library, just to use that one method to do diddley?)

What does all this mean?

It means that:

  • The original OS map will be used as originally intended with one dot for every BTS
  • The original SQL ER diagram will be used as intended
  • The original module structure will be used as intended but expanded, reduced and revised
  • The core network data collector will need to be re-written for efficiency and to use all features
  • The AT command shell will be removed moved to a "collector".
  • The neighboring cell shit for Samsung will be removed moved to a "collector".
  • The Femto cell shit will be removed
  • The silent SMS detector will be re-instated as originally working
  • The manual BTS antenna map placement will be developed
  • Nothing will be uploaded to any servers (Dumb people and shitty apps just spam & upload wrong data.)
  • Nothing will be downloaded from any servers, except Map tiles and maybe limited MLS data.
  • A wrapper download app will be on Google Play. That app will check and download latest AIMSICD and check the app signature and hash. Signature certificate will be held by me and one other trusted person, only.
  • I reserve my right to amend to this list, as I'm sure I've forgotten loads of other things.

Anyway, this is just a suggestion that I have not yet decided on. But it is for sure the only condition I would accept, in order to continue on this project. Feel free to burn me or support me. I happy to hear your opinions either way.

Assignee
Assign to
Time tracking