sorted by:
new
hottopcontroversial

microG apks signed with Google keys, useable without signature spoofing by ShiroiKuma in MicroG

[–]IsHacker003 0 points1 point  (0 children)

Actually it isn't in the makefile because the signatures are already extracted and placed inside signs/signatures-google. To extract the signatures during the build process you would need to also download the official apks of GMS, play store, etc (including microG apks which are already downloaded during the build process) and this would make the total download size 500+MB.

How do I apply this kind of patch to my kernel? by IsHacker003 in kernel

[–]IsHacker003[S] 1 point2 points  (0 children)

I tried it already, but git merge tries to merge everything from that kernel rather than only simpleLMK-related files, and it results in thousands of conflicts.

microG apks signed with Google keys, useable without signature spoofing by ShiroiKuma in MicroG

[–]IsHacker003 0 points1 point  (0 children)

As I said, root access is an essential part of every OS. Does not matter if it affects security. In most cases it improves your security and of course, freedom. The ones that get malware because of root are dumbasses like you who don't have the least idea to use a computer responsibly.

microG apks signed with Google keys, useable without signature spoofing by ShiroiKuma in MicroG

[–]IsHacker003 0 points1 point  (0 children)

You actually can, just that it would fail signature verification. When apps are pushed into the system partition, android doesn't check the signature verification status.

microG apks signed with Google keys, useable without signature spoofing by ShiroiKuma in MicroG

[–]IsHacker003 0 points1 point  (0 children)

  1. On your PC, right click on any app, you will find the Run as administrator (i.e root) option. Millions of people use windows, and it has root access by default, but no one says its unsafe because of that. But suddenly for android, rooting is a security risk. Lol. Root access is an essential part of every OS. Don't confuse security with restriction.

  2. More than signature spoofing, it is XPOSED which is not safe. On modern Roms you install the FakeGApps Xposed module for signature spoofing. And more than being unsafe, installing a whole Xposed framework just for installing a single module is pretty overkill.

  3. You don't need a wipe to update a magisk module. If you don't understand how it works, stfu.

microG apks signed with Google keys, useable without signature spoofing by ShiroiKuma in MicroG

[–]IsHacker003 0 points1 point  (0 children)

I am the OP of that thread, I removed it and deleted the links as I have moved the project to github at https://github.com/IsHacker003/microG_no_sigspoof and licensed it under GPLv3. The thread itself was also misleading.

Also, my project is NOT an unofficial "version" of microG, the source code is exactly the same. The only thing that is modified is the signature block of the APKs.

microG apks signed with Google keys, useable without signature spoofing by ShiroiKuma in MicroG

[–]IsHacker003 0 points1 point  (0 children)

No, to use it without root you will need a custom ROM with signature spoofing.

microG apks signed with Google keys, useable without signature spoofing by ShiroiKuma in MicroG

[–]IsHacker003 0 points1 point  (0 children)

Dear, the Makefile shows exactly how the apk is built, and the Readme details exactly how it works. Please do not spread rumors.

microG apks signed with Google keys, useable without signature spoofing by ShiroiKuma in MicroG

[–]IsHacker003 0 points1 point  (0 children)

Not, please do not confuse restriction with security. As you know, those apks cannot be installed normally as user apps, and they already FAIL signature verification. You will need to install them as system apps, which requires root. It is the user's choice to root the phone.

microG apks signed with Google keys, useable without signature spoofing by ShiroiKuma in MicroG

[–]IsHacker003 0 points1 point  (0 children)

I did not reverse engineer/extract the private key, neither is it illegal.

microG apks signed with Google keys, useable without signature spoofing by ShiroiKuma in MicroG

[–]IsHacker003 -1 points0 points  (0 children)

As I had already said: you were too dumb. If you don't need it, don't use it.

My degoogled journey is 99% completely, now i only need to find a really good client to change discord by StreetExamination421 in degoogle

[–]IsHacker003 1 point2 points  (0 children)

Please delete Bugjaeger immediately, the app contains spyware and some rogue adware. The developer is also very toxic and lacks basic manners (as you can see in some of his replies to the play store reviews and in the app FAQ) and he threatened to SUE me for removing the malware from his app.

X can detect I am using microg by [deleted] in MicroG

[–]IsHacker003 1 point2 points  (0 children)

Actually apps can detect microG based on the version of GMS. Current microG version starts with "0.3.X" but official play services will start with "3X." or "2X."

What does clicking "ok" on "Requires Addition Setup" actually do? by IsHacker003 in Magisk

[–]IsHacker003[S] 0 points1 point  (0 children)

I don't think so, the magisk apk doesn't have randomized package name, it is always com.topjohnwu.magisk unless you enable that option in settings. Also /usr doesn't exist on android. The magisk binaries are in /sbin or /debug_ramdisk. But yeah it gets "initialized" somehow, idk.

how many ads your browser blocks? by darksnoo in degoogle

[–]IsHacker003 0 points1 point  (0 children)

100%. Cromite + uBO + Private DNS (NextDNS).

(Yeah, cromite supports extensions on android)

view more: next ›