Samsung Left Millions Vulnerable To Hackers Because It Forgot To Renew a Domain (vice.com) 54
An anonymous reader writes: Samsung cellphones used to have a stock app called S Suggest. The company apparently discontinued the app recently, and then forgot to renew a domain that was used to control it. This snafu left millions of smartphone users vulnerable to hackers who could've registered the domain and installed malicious apps on the phones.
what happens if a company goes under (Score:4, Interesting)
What would have happened with something like this if a company goes under?
We almost need a charity foundation of some sort to maintain domains like this in that situation.
Re: (Score:3)
Then there needs to be an officer in the company who is responsible to activate this mechanism in the event that the company ceases operations. Prior to that happening, the product manager of the affected product would be responsible to use this mechanism to disable further updates to the app when it is being discontinued.
Re: (Score:2)
ah, script kiddies newest target, that mechanism. render massive slice of a market unable to use their internet dependent product.
Re: (Score:2)
You can disable any app in Android. Instead of "uninstall" you'll see a button to uninstall updates, then if you uninstall updates you'll see a button to disable the app.
Re: (Score:2)
You can disable any app in Android. Instead of "uninstall" you'll see a button to uninstall updates,
Most user loaded apps do not have a "disable" feature. It's either let it run as it wants or uninstall it lock, stock and barrel.
I wish they all had "disable", since there are apps (like Nook with at least 5, FileManager+ with one, Accuweather with 3 or 4) that run multiple services all the time, even when you haven't used the app for a month. And some of them simply won't go away when you kill them (Google Location Services service, I'm pointing at you.) It's a pain to have to uninstall apps and then rei
Re: (Score:2)
You can disable any app in Android. Instead of "uninstall" you'll see a button to uninstall updates,
Most user loaded apps do not have a "disable" feature. It's either let it run as it wants or uninstall it lock, stock and barrel.
Like I said, if you've been paying attention, " Instead of 'uninstall' you'll see a button to uninstall updates".
If a user installed it, you'll just see "uninstall". If it's a factor app you'll get the "uninstall updates" -> "disable".
Of course Android is different with every OEM, but I haven't run into any that totally prevented me from disabling an OEM app. Samsung's definitely gives you scary warnings if you attempt it but it lets you.
Re: (Score:2)
Like I said, if you've been paying attention, " Instead of 'uninstall' you'll see a button to uninstall updates".
And like I said, if you had been paying attention, is that most USER LOADED apps do not have a disable feature. Many system apps do, but user installed do not. It would be a good feature for the user to have to be able to disable instead of uninstall those apps.
If it's a factor app you'll get the "uninstall updates" -> "disable".
Which does not contradict in any way what I said about user-installed apps, so keep your insults to yourself.
Of course Android is different with every OEM, but I haven't run into any that totally prevented me from disabling an OEM app.
For just one example, I have a factory test app that becomes active every time I reboot one of my Samsung tablets. I can kill it and it will
Re: (Score:2)
Re: (Score:2)
Oh you really zinged me. Yes I said "any app". I should have said something like "any app that the article was talking about"
I don't care what you think you want to do. Android lets you disable factor apps, except in the rare cases the vendor hacks that feature out. Users can either have additional apps installed or if they don't want to use them, not have them installed. That's the model, we all understand that you don't like that model, but that's how it works today. The functionality is effectively equiv
Re: (Score:2)
I don't care what you think you want to do.
Thanks.
Android lets you disable factor apps, except in the rare cases the vendor hacks that feature out.
As I pointed out already, the survey of "factor" apps I made on my Samsung device showed less than 50% of them could be disabled. It isn't rare if more than 50% of the apps cannot be disabled.
Users can either have additional apps installed or if they don't want to use them, not have them installed.
Of course. But that means that any app that a user needs only occasionally must be reinstalled from scratch before it can be used for a short period of time, and then re-uninstalled. That's a lot more work that simply disabling/enabling/disabling an app. This difference seems to be lost on you. For example, the
Re: (Score:2)
And like I said, if you had been paying attention, is that most USER LOADED apps do not have a disable feature. Many system apps do, but user installed do not. It would be a good feature for the user to have to be able to disable instead of uninstall those apps.
Yes, you'd uninstall those, not disable them. Fucking idiots these days.
Re: (Score:2)
Yes, you'd uninstall those, not disable them. Fucking idiots these days.
You clearly do not understand the difference between disabling an app and uninstalling them. As I said a couple of times now, it would be nice if we could disable any app LIKE YOU SAID WE CAN, but which in truth cannot be done. You are not in a good position to be using insult to make your point.
Re: (Score:2)
Re: (Score:2)
Re: (Score:2)
Neither of those things will help, unfortunately.
Normal people don't install updates unless forced to. If it isn't 100% automatic it isn't happening. And anyway, how would they even know to disable the app? Most don't read security advisory mailing lists.
Giving someone the job of handing over company assets for free to a charity at the precise moment that the company is being broken up for scrap isn't likely to fly either. They would just get blamed for giving away something that the bankruptcy team could h
Re: (Score:2)
Re: (Score:2)
Re: (Score:2)
What would have happened with something like this if a company goes under?
For one thing, you should have some kind of authentication. Basing security entirely around domain name is a known security flaw, since at least the 90s. Two to one odds says that they also programmed the app to communicate over HTTP instead of HTTPS.
Proprietary SW is the bug. SW freedom is the fix. (Score:2)
What users need is software freedom (the freedom to run, edit, and share the complete corresponding source code to the software) so they can alter the software as they wish, point the device to whatever site they want for updates, and genuinely own their computers. There's no good reason to keep a domain going and address this in a monopoly-sustaining surface level way. Keeping a domain going is not really the issue nor is that a thorough solution to the underlying problem.
Re: (Score:1)
What users need is software freedom (the freedom to run, edit, and share the complete corresponding source code to the software) so they can alter the software as they wish, point the device to whatever site they want for updates, and genuinely own their computers.
You already can. Just buy the appropriate hardware for whatever software you have rights to and want to install on it. Enjoy.
Also (Score:2)
Re: (Score:2)
Re: Also (Score:2)
Zero risk if done right (Score:3)
It doesn't matter who controls or hijacks your domain because DNS is not an authoritative source of information. You go through numerous unsigned caches before you get queries through.
If you write software without your head up your ass you'd use a certificate on the app to check every interaction with the server before you trust it.
Re: (Score:2)
Yes but these are the same type of programmers that think that doing the error checking in Javascript is good enough.
You Fail It (Score:1)
I hope our goatse guy gets his domain renewed soon. I'd hate to see him fall victim to the same problem!
Why did they even need a separate domain for this? (Score:5, Insightful)
You'd think they could have instead used "ssuggest.samsung.com" or similar, rather than registering an entirely separate domain for what is essentially a minor feature on a phone.
The nice thing about DNS is that it was designed PRECISELY TO BE USED THIS WAY, being able to establish a hierarchy so that an entity can organize all their hostnames/services in one hierarchy.
Re: (Score:2)
Re: (Score:1)
Your bitterness is misplaced in this case. The proper response is "Of course we can handle 'yourdomain.com'. You filled out this form and had the company (me) add the domain to our list of supported names (and added the appropriate SMTP clauses to our DNS servers) so we register correctly with the blacklisting services?" as a start. Putting the situation into a "we have these processes and abilities to support you, let's confirm you followed the steps" scenario without being defensive from the start, if don
But "Touchwiz isn't so bad..." (Score:2)
Plus all of those Samsung crap apps.
That's why I use stock Android on my Nexus, and my next phone will be a Pixel. It's a shame because the Samsung hardware is really nice (except the Galaxy S7 of course).
Re: (Score:2)
The cloud is great... (Score:2)
at fucking you over. ;)
I quit using the "smart" features (Score:1)
Yeah, BUT.... (Score:2)
Yeah, but they saved $9.99 by not renewing the domain so it was a huge win for Samsung.
It couldn't happen: it's a Samsung phone. (Score:2)
It self destroys by design, hackers don't have enough time to compromise the phone.