Grant Joseph

https://mastodon.social/@GrantJoseph

Cybersecurity student. Lover of all things computer science.

Blog: https://grantljoseph.github.io
Email: grantjoseph12@protonmail.com
X/Twitter: https://x.com/GrantLJoseph

Public Key

npub14gqwqjyq0nzz4kvdsp0rfkla0asgxfvke7f0dtaym6y6p363aq3qaxx6uv

NIP-05 Address

grantjoseph_at_mastodon.social@momostr.pink

Profile Code

nprofile1qqs25q8qfzq8e3p2mxxcqh35m07h7cyryktvlyhk47jdazdqcag7sgs6keq9q

Author Public Key

npub14gqwqjyq0nzz4kvdsp0rfkla0asgxfvke7f0dtaym6y6p363aq3qaxx6uv

Show more details

Last Notes

2025-04-12 10:45:36

- reply

Ah I remember there being a controversy around that a while back. Are the changes no longer needed because the currently supported devices don't use Qualcomm GPS?

2025-04-12 03:28:39

- reply

Could I have some context for what the Qualcomm GNSS privacy issues were?

2025-03-27 10:32:34

- reply

What is the difference between an attestation purpose key and a regular key with attestation enabled? That's where I get confused. I'm also not following what the unused key is for if it's not used.

2025-03-25 10:11:33

@npub1kwa…e0nj Do you have any good resources you could share about how attestation key provisioning works in detail? My understanding is it used to use a batch key from the factory. Now it uses a unique key but only to provision keys from Google. These keys have no chain to the permanent device key so the key recipient and Google would have to work together to uniquely identify a device. Is that right?