News for hackers. Stuff that matters.
Re:Librarian's Letter to Google Security by antgiant on Monday August 01, 2022 @10:59AM (#32306893)
If the US government created its own SSO system and mandated that all government website used it as primary while allowing third parties to use it too this could become a solved problem. It would be a credential that could be accessed via existing paper based systems. Places like Google allowing it as a sign in method would actually solve this case. Sadly I think the tech world in general is so allergic to losing privacy that even something optional like this would get lobbied out of existence just by tech companies alone.
Re:Librarian's Letter to Google Security by zie on Monday August 01, 2022 @11:04AM (#32306981)
login.gov exists. It's not mandated, nor does it currently allow non-government users(last I checked), but otherwise it generally solves the technical problems fine.
Re:Librarian's Letter to Google Security by jackson1442 on Monday August 01, 2022 @01:07PM (#32309082)
You can sign-in as a non-government user (though they also have CAC support for federal govt users). There's built-in document/identity proofing as well but there are some extra requirements to get that enabled on an application.

You do need to be working with the government to integrate with Login.gov though (but it's just OIDC on the backend)

Re:Librarian's Letter to Google Security by antgiant on Tuesday August 02, 2022 @02:19PM (#32322395)
That is perfect! Just need it to be opened up a little so that places like Google can enable it as a Lyn optional primary login.
Re:Librarian's Letter to Google Security by dtertman on Monday August 01, 2022 @11:24AM (#32307345)
It's used to manage your Global Entry membership.