microg / microg/GmsCore

Support for the upcoming reCAPTCHA changes

Open
#3,455 4 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

**Is your feature request related to a problem? Please describe.**
A clear and concise description of what the problem is. Google are planning to or already are rolling out a new version of reCAPTCHA called "Cloud Fraud Defence". If any traffic is flagged as suspicious, instead of a typical clicking boxes activity, a modern iPhone or a phone with GMS is used to scan a QR code to verify instead. This is fairly concerning for phones running microg as there's a risk people get locked out of parts of the internet.

Google article linked for info:
https://cloud.google.com/blog/products/identity-security/introducing-google-cloud-fraud-defense-the-next-evolution-of-recaptcha

**Describe the solution you'd like**
A simple button somewhere in the app to activate a QR scanner for the user to scan the code that pops up on the reCAPTCHA window.

**Describe alternatives you've considered**
One could carry around a second phone, or use a good VPN to make their traffic seem less suspicious(which is fairly rare nowadays) or find some other way to get the non QR code reCAPTCHA test.

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

No file or test is named. Start by locating the Android UI and verification entry points related to reCAPTCHA, then read the linked Google article to confirm the expected QR flow. Done means users can reach a QR-scanning action in the app and use it to complete the QR challenge shown by reCAPTCHA.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, java
Domain
mobile, security
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.