jzy/TEESimulator-RS
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(spoof): explain MAX_FUTURE_DAYS rationale

Browse Source 
The 60-day window covers Pixel monthly bulletin cadence plus
pre-announcement slip but rejects far-future hostile inputs. The
prior bare constant left readers wondering whether the value was
arbitrary; the KDoc closes that loop.
This commit is contained in:
Enginex0
2026-05-19 05:35:40 +01:00
parent fbe819d6d8
commit 393ae6073f
1 changed files with 6 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
app/src/main/java/org/matrix/TEESimulator/config/PatchLevelManager.kt
+6
View File
@@ -17,6 +17,12 @@ object PatchLevelManager {
private const val PIF_DIR = "/data/adb/modules/playintegrityfix" private const val PIF_DIR = "/data/adb/modules/playintegrityfix"
private const val FLOOR_YYYYMMDD = 20200101 private const val FLOOR_YYYYMMDD = 20200101
private const val MAX_PAST_OFFSET = 10000 private const val MAX_PAST_OFFSET = 10000
/**
* Pixel security bulletins publish monthly; pre-announced dates occasionally
* slip by 2-4 weeks. 60 days covers that window without admitting a
* far-future date from a hostile or mis-parsed bulletin response.
*/
private const val MAX_FUTURE_DAYS = 60L private const val MAX_FUTURE_DAYS = 60L
private val PIF_FILENAMES = private val PIF_FILENAMES =