Device attestation results collapse to verified, unverified or unknown, with values sanitised.
What's wrong with this entry?
Raw attestation strings are now mapped to just "verified", "unverified" or "unknown", with the internal prefix stripped and the gate-verified, keyless-device and service-vouched variants all folded into "verified", absent and invalid into "unverified". A companion sanitiser truncates values to 64 characters and replaces non-printable bytes with "?".
DEVICE_ATTESTATION_STATUS_
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.239
Trusted-device enrollment now happens on demand, not just up front
Both mention device trust
-
v2.1.239
Remote sessions can re-enroll a device after a 403 and retry
Both mention device trust
-
v2.1.246
Machine list says which machine your project is on
Both mention device