2024-05-02 19:06 UTC
Replies (3)
-
@briankrebs@infosec.exchange 2024-05-02 19:13
How about this? Lawmakers pass a law (gasp!) that says if you're a private company providing services to the entire populace on behalf of .gov, your site will use com/net/org only when it is interacting with the government. Full stop. Probably even the extreme wingnuts in the GOP could get behind this, in a kind of "buy American" way.
-
@tychotithonus@infosec.exchange 2024-05-02 19:11
@briankrebs@infosec.exchange I'm also mystified why they didn't just extend the capabilities of login.gov to cover the "check their driver's license" aspects of ID.me, and keep the entire thing in house. login.gov's design and UX is thoughtfully, expertly executed, is vastly superior to ID.me, and is already under .gov and championed by 18F. But instead of pushing login.gov everywhere (which was the orignal plan), ID.me materialized and pushed its way into IRS and pay.gov in a way that seemed weirdly pre-emptive of the entire login.gov effort.
-
@philip@mastodon.mallegolhansen.com 2024-05-02 19:29
@briankrebs@infosec.exchange I really wish everyone in general, and government institutions in particular, would take to heart the hierarchical nature of domains. (Putting aside the preferential nature of .gov being US only, and not for all government) Give us irs.federal.gov, legislature.wa.gov, etc! I should be able to trust at a glance that something is the product of my state government based on the domain.