Skip to content
This repository has been archived by the owner on Sep 6, 2019. It is now read-only.

Improve restricting IMSI #1201

Closed
Cyclu opened this issue Jan 30, 2014 · 4 comments
Closed

Improve restricting IMSI #1201

Cyclu opened this issue Jan 30, 2014 · 4 comments

Comments

@Cyclu
Copy link

Cyclu commented Jan 30, 2014

With Elixir2 I can read IMSI MCC+MNC with /system/build.prop restricted (has the usage data) restricting shell/exec has not effect here like for hostname as I said in the another issue. In the build.prop I found this two prop:
gsm.operator.numeric]: [00101] MCC+MNC
gsm.sim.operator.numeric]: [00101] MCC+MNC

With Elixir2: Open Information screen>go into software page with right arrow>tape Configuration>More Information

screenshot_2014-01-29-37-18-47

@M66B
Copy link
Owner

M66B commented Jan 30, 2014

I do not really understand why you can get the mcc/mnc this way, but I will restrict it:
http://developer.android.com/reference/android/content/res/Configuration.html

@Cyclu
Copy link
Author

Cyclu commented Jan 30, 2014

Really I don't know why it see the usage data for the build.prop you have the same result with Elixir?

M66B pushed a commit that referenced this issue Jan 30, 2014
@M66B M66B closed this as completed in de8044e Jan 31, 2014
@Cyclu
Copy link
Author

Cyclu commented Jan 31, 2014

Even if I access directly to this screen in the Elixir2 I has the usage data for build.prop surely it's
a coincidence. Restriction works perfectly we have the fake data!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants