The reqTime/recvTime fields of the no-valid-mapx-fb-rmd value. The
app writes two 32-bit numbers there that it never computes: they match no
/rmd request/response time or clock, and they differ from one run of the
app to the next. The twelve numbers of the apps (Android 448 and 451 and
the iOS 451 launch) are four printable ASCII bytes read
little-endian, zero or other leftover bytes: uninitialised memory. They
derive from nothing, so each
install keeps its own pair, generated once (rmdNoValidMapTimesOf) and
stored on the device; a scenario's device declares the pair it starts with, and the
comparison keeps them literal. Strings keep the pair opaque (they are not
usable timestamps).
The
reqTime/recvTimefields of theno-valid-mapx-fb-rmdvalue. The app writes two 32-bit numbers there that it never computes: they match no/rmdrequest/response time or clock, and they differ from one run of the app to the next. The twelve numbers of the apps (Android 448 and 451 and the iOS 451 launch) are four printable ASCII bytes read little-endian, zero or other leftover bytes: uninitialised memory. They derive from nothing, so each install keeps its own pair, generated once (rmdNoValidMapTimesOf) and stored on the device; a scenario's device declares the pair it starts with, and the comparison keeps them literal. Strings keep the pair opaque (they are not usable timestamps).