Event JSON
{
"id": "e5535821255277351eed326b688963426aa1a2b8ac0cb48519eb9b12ce629c22",
"pubkey": "0f2f4155530e92d11d0942a11a701e1cba02db35dd2990493f4bcb739f7f1065",
"created_at": 1763412067,
"kind": 1,
"tags": [
[
"proxy",
"https://infosec.exchange/@cyberseckyle/115566973238147534",
"web"
],
[
"t",
"chrome"
],
[
"t",
"privacy"
],
[
"t",
"cybersecurity"
],
[
"t",
"infosec"
],
[
"proxy",
"https://infosec.exchange/users/cyberseckyle/statuses/115566973238147534",
"activitypub"
],
[
"L",
"pink.momostr"
],
[
"l",
"pink.momostr.activitypub:https://infosec.exchange/users/cyberseckyle/statuses/115566973238147534",
"pink.momostr"
],
[
"-"
]
],
"content": "Chrome now wants to store and autofill your driver’s license and other ID info.\n\nFrom a cybersecurity perspective, that is a hard no from me. Info-stealer malware already targets browser autofill, and you cannot rotate a driver’s license number like a password. Putting high value IDs in the most targeted consumer app on the planet is a bad trade for a little convenience.\n\nI wrote up why this feature is such a risky idea and what I recommend instead:\n\n🔗 https://www.kylereddoch.me/blog/chromes-new-drivers-license-autofill-is-a-terrible-idea/\n\n#Infosec #Privacy #Chrome #Cybersecurity",
"sig": "c8f6295b492c8e4bde7eff788e2915e0d92f0bc638050e0850e6195a81de4496cc171fc2a43b304ccfb935fc8210237a4b976174498d1f12f117b4da10f287d0"
}