29 ms·
This is kinda cool, but it's also a little concerning. One of the ways our government protects our privacy is specifically by not centralizing information. Just
by ocdtrekkie 9y ago
This is kinda cool, but it's also a little concerning. One of the ways our government protects our privacy is specifically by not centralizing information. Just because you pay taxes or have healthcare doesn't mean the police has that info, for example. The efficiency of connecting a large number of governmental agencies to a single account for you is pretty concerning, it puts all the data in one spot that can be extremely tempting to access.
- dkhenry 9y agoIts important to remember that login.gov isn't an account its an Identity Provider. It will allow you to prove to an agency that you are who you say you are, but all the account information will be stored by the agency.
- sharemywin 9y agoyou know what I like about google+ if someone miss uses it I don't really care. I don't use it for anything Important.
- dragonwriter 9y ago> Its important to remember that login.gov isn't an account its an Identity Provider. Doesn't matter, the consequenes are the same. If it is compromised or exploited (internally or externally) the exploiter can access all of your information from, and impersonate you too, all the government systems that rely on it for identity.
- dkhenry 9y agoI don't think that was the concern being expressed by the grandparent. If the concern was the government now has a secret trove of all your information this specific product doesn't change anything on that front as it doesn't store your information it just acts as an identity provider. If the concern is exploiting this one account allow an attacker to get at all your government systems, then yes this is a new treasure trove. I am going to fall on the side of its better to have one secure account then 100 different less secure accounts. I think the industry has found this to be the case and widespread use of Password Managers and Oauth based logins backs me up on that.
- dragonwriter 9y agoI'm not saying that it's not better net, I’m saying that, insofar as there is an internal or external risk of compromise or abuse, a single government identity provider poses the same kind of risk as a single government profile would provide.
- Joeri 9y agoI pity the fool who hacks such a strategic government service. The expression "threw away the key" comes to mind for what might happen to them.
- dragonwriter 9y agoImproper (but not necessarily unsupported from above) internal use is at least as worrisome as hacking, and centralization reduced the size of the necessary conspiracy and the probability of detection and whistleblowing.)
- skybrian 9y agoWill it? Apparently login.gov doesn't even ask for your real name?
- ocdtrekkie 9y agoSure, but other services using it will. And the login.gov account will be a handy new primary key for relating disparate databases across government resources.
- sharemywin 9y agoObviously it's not going to get hacked or anything...I mean once an organization gets so big it's vastly better at keeping it from getting hacked...
- oh_sigh 9y agoI know I'm not supposed to say this, but you obviously either didn't read the article or read it but didn't understand it, and perhaps you would be better off reading it more closely before commenting. The article lays out that this is not centralizing information, but is merely allowing a bunch of different agencies to use it as an identity provider. The same way I can, say, connect to my spotify via my Google+ account, but that doesn't mean that google has all of my spotify playlists.
- ocdtrekkie 9y agoI, uh, skimmed it. But bear in mind, once your data is already handily collated by a common system/identifier, it's one policy change from being able to automatically connect that information and make it available.
- blfr 9y agoYes but anyone who pops your Google+ account can get all your playlists.
- josefresco 9y agoIn the case of Google, you can trust their security over the (usually) much smaller vendor. With this? Not so much.
- grzm 9y ago> I know I'm not supposed to say this, but you obviously either didn't read the article If you're referring to the guidelines, they also show how leaving out sentiments like these doesn't diminish the clarification you're adding: > Please don't insinuate that someone hasn't read an article. "Did you even read the article? It mentions that" can be shortened to "The article mentions that."[0] https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/newsguidelines.html Chiding someone who is trolling isn't going to accomplish anything (and likely make it worse). If they aren't, they'll (hopefully) appreciate the clarification, no chiding necessary.
- 9y ago
- hartator 9y agoI don't get why you downvoted. One phishing on your healthcare plan and you loose access to your taxes.
- nicodjimenez 9y agoIt's hard to say that our government really protects our privacy by scattering copies of our information across a constellation of bureaucracies. And protect from who? Who's really more dangerous than our government itself? login.gov is obviously a good idea. Can you imagine how awful government website's internal authentication software must be? This is like Auth0 for government agencies. It will probably be 10x worse than Auth0 but 10x better than the atrocities probably being committed right now.