microg / microg/GmsCore

Info about fake-signature module

Open
#2,037 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

question
Dominant language
Java
Stars
14.6k
Forks
3.2k
Avg merge
12d 11h
Merged PRs (30d)
4

Description

@mar-v-in

Hi,
I have some questions:

  1. What happens to packages that are neither in signature_want_fake or signature_never_fake?
  2. If it is signed with a different signature does also the real_signature inside signature.xml need to be replaced?
  3. What does all the new meta-data inside AndroidManifest.xml mean?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the fake-signature module and inspect the signature_want_fake and signature_never_fake settings, signature.xml, and AndroidManifest.xml. Document what happens for packages outside those settings, how real_signature is handled, and what the new manifest metadata means; the issue is done when all three questions have clear answers.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, java
Domain
documentation, mobile
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.