Skip to content

RealJohnGalt/KeyBoxRevocationResearch

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 

Repository files navigation

Simple research project:

  • Utilize a simple script to check a large repository of leaked Android device keyboxes against googleapi revocation status to determine preferential treatment.
  • Hourly it batch checks and git pushes. If there are no changes, the commit is not pushed (due to being empty).
  • We regulary see A-tier (so to speak) companies being given preferential treatment. This can be seen with known leaked keyboxes from Samsung being given extraordinarily long rollover periods. During these periods, Google continues attesting them as strong, despite knowing it may not even be a Samsung device or a strong attested device making the request! It's that untrustworthy of a system to begin with! Meanwhile smaller smartphone companies with smaller userbases get their keys revoked immediately, negatively affecting these lower-class (non A-tier device) users.

About

A repository to test how monopolistic/preferential Google's treatment of smartphone companies is

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published