I understand that a device attestation includes extra attestation identifier tags like:
ATTESTATION_ID_BRAND
ATTESTATION_ID_DEVICE
ATTESTATION_ID_PRODUCT
ATTESTATION_ID_SERIAL
ATTESTATION_ID_IMEI
ATTESTATION_ID_MEID
ATTESTATION_ID_MANUFACTURER
ATTESTATION_ID_MODEL
ATTESTATION_ID_IMEI_2
ATTESTATION_ID_MEID_2
Currently, I'm not sure if this data is missing or random? It could be useful to be able to configure these values in a config file.
An example use case is for an RKP eligible device that is using a factory keybox obtained from an older device. Currently there is no attempt to block this and enforce use of RKP, but in future that may change. It might be helpful to spoof an older device by providing attestation extension data that matches the details of the device from which the keybox was originally obtained. Of course there will always be other detection methods, but it would still be an improvement.
This is an example of a repo aiming to allow customization of such identifiers, but it doesn't combine this with a keybox and actual attestation chain, whereas perhaps TS could add this data to the existing functionality? I am not sure why it would need to be customisable per package (like below) - the same config data could be used for any targeted apps.
https://github.com/StevenWin818/Identifier-Patcher
I understand that a device attestation includes extra attestation identifier tags like:
ATTESTATION_ID_BRAND
ATTESTATION_ID_DEVICE
ATTESTATION_ID_PRODUCT
ATTESTATION_ID_SERIAL
ATTESTATION_ID_IMEI
ATTESTATION_ID_MEID
ATTESTATION_ID_MANUFACTURER
ATTESTATION_ID_MODEL
ATTESTATION_ID_IMEI_2
ATTESTATION_ID_MEID_2
Currently, I'm not sure if this data is missing or random? It could be useful to be able to configure these values in a config file.
An example use case is for an RKP eligible device that is using a factory keybox obtained from an older device. Currently there is no attempt to block this and enforce use of RKP, but in future that may change. It might be helpful to spoof an older device by providing attestation extension data that matches the details of the device from which the keybox was originally obtained. Of course there will always be other detection methods, but it would still be an improvement.
This is an example of a repo aiming to allow customization of such identifiers, but it doesn't combine this with a keybox and actual attestation chain, whereas perhaps TS could add this data to the existing functionality? I am not sure why it would need to be customisable per package (like below) - the same config data could be used for any targeted apps.
https://github.com/StevenWin818/Identifier-Patcher