Remote DroidGuard runtime for public use?
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 14.6k
- Forks
- 3.2k
- Avg merge
- 12d 11h
- Merged PRs (30d)
- 4
Description
There's no documentation about the Remote option in DroidGuard operation mode.
Let me guess: if local, the verification is done on same device as microG is running, otherwise is done remotely on another device.
Can we just make a bootloader locked, stock system, innocent device a public DroidGuard runtime server to pass SafetyNet?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file or test is named. Start by tracing the Remote option in DroidGuard operation mode and reviewing any existing documentation, then determine whether a public runtime server is supported. Done would require a documented explanation of local versus remote verification and a clear answer about the feasibility and security implications of public use.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, java
- Domain
- documentation, mobile-dev, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100