From 62d666fd63bebfa30ae41cbf28ad1d97810ad8aa Mon Sep 17 00:00:00 2001 From: Enginex0 Date: Tue, 19 May 2026 05:35:40 +0100 Subject: [PATCH] docs(spoof): explain MAX_FUTURE_DAYS rationale 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. --- .../org/matrix/TEESimulator/config/PatchLevelManager.kt | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/app/src/main/java/org/matrix/TEESimulator/config/PatchLevelManager.kt b/app/src/main/java/org/matrix/TEESimulator/config/PatchLevelManager.kt index e94d6c6..d92cec2 100644 --- a/app/src/main/java/org/matrix/TEESimulator/config/PatchLevelManager.kt +++ b/app/src/main/java/org/matrix/TEESimulator/config/PatchLevelManager.kt @@ -17,6 +17,12 @@ object PatchLevelManager { private const val PIF_DIR = "/data/adb/modules/playintegrityfix" private const val FLOOR_YYYYMMDD = 20200101 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 val PIF_FILENAMES =