Daniel Micay comments

Results 1141 comments of


                                            Daniel Micay

Add support for the Samsung Galaxy Z Flip3 5G (SM-F711B)

@dbaxa Gave some information to @flawedworld about what is needed to build a tool for generating the data from samples and verifying samples automatically.

Add support for the Samsung Galaxy Z Flip3 5G (SM-F711B)

I got tired of doing it by hand. It's too time consuming to copy paste them in base64 format into that array and verify with the app with multiple steps....

StrongBox keys sometimes have KM_TAG_CREATION_DATETIME set to an enormous value - could also be an issue in the libraries parsing the certificates (BouncyCastle) but that seems less likely

% factor 18446744073709546693 18446744073709546693: 7 2635249153387078099

StrongBox keys sometimes have KM_TAG_CREATION_DATETIME set to an enormous value - could also be an issue in the libraries parsing the certificates (BouncyCastle) but that seems less likely

I've reproduced this on both GrapheneOS and the stock OS.

StrongBox keys sometimes have KM_TAG_CREATION_DATETIME set to an enormous value - could also be an issue in the libraries parsing the certificates (BouncyCastle) but that seems less likely

A different one this time: 18446744073709031998. % factor 18446744073709031998 18446744073709031998: 2 59 46639 3351880177699

StrongBox keys sometimes have KM_TAG_CREATION_DATETIME set to an enormous value - could also be an issue in the libraries parsing the certificates (BouncyCastle) but that seems less likely

It does seem to be counting like a timer: >>> 2**64 18446744073709551616 >>> 2**64 - 18446744073709031998 519618 >>> 2**64 - 18446744073709203078 348538 >>> 2**64 - 18446744073709223973 327643 >>> 2**64 -...

StrongBox keys sometimes have KM_TAG_CREATION_DATETIME set to an enormous value - could also be an issue in the libraries parsing the certificates (BouncyCastle) but that seems less likely

``` >>> 2**64 - 18446744073709535336 16280 ```

StrongBox keys sometimes have KM_TAG_CREATION_DATETIME set to an enormous value - could also be an issue in the libraries parsing the certificates (BouncyCastle) but that seems less likely

It wrapped around and started working again: ```` 04-26 07:23:25.564 19155 22122 I Attestation: Parsing tag: [701], value: [103581] 04-26 07:24:05.990 19155 22904 I Attestation: Parsing tag: [701], value: [145820]...

StrongBox keys sometimes have KM_TAG_CREATION_DATETIME set to an enormous value - could also be an issue in the libraries parsing the certificates (BouncyCastle) but that seems less likely

This is worked around by 8137ab5375a66c27b3c5b88c74bd89557ae0a950.

UserManager.getUserCount would be useful but requires signature|privileged

There might be a device manager equivalent to this too.