Replicant Hackers Find and Close Samsung Galaxy Back-door 81
gnujoshua writes "Paul Kocialkowski (PaulK), a developer for the Replicant project, a fully free/libre version of Android, wrote a guest blog post for the Free Software Foundation announcing that whlie hacking on the Samsung Galaxy, they "discovered that the proprietary program running on the applications processor in charge of handling the communication protocol with the modem actually implements a back-door that lets the modem perform remote file I/O operations on the file system." They then replaced the proprietary program with free software.
While it may be a while before we can have a 100% free software microcode/firmware on the the cellular hardware itself, isolating that hardware from the rest of your programming and data is a seemingly important step that we can take right now. At least to the FSF anyhow. What do others think: is a 100% free software mobile device important to you?"
While it may be a while before we can have a 100% free software microcode/firmware on the the cellular hardware itself, isolating that hardware from the rest of your programming and data is a seemingly important step that we can take right now. At least to the FSF anyhow. What do others think: is a 100% free software mobile device important to you?"
Who's behind that back-door ? (Score:2)
NSA ?
GCHQ ?
Or their equivalent from South Korea ?
Re: (Score:1)
I really hope you didn't type that out.
Re: (Score:1)
Holy batshit, er, batman.
Comment removed (Score:5, Interesting)
Re: (Score:2)
This was my exact thought when I read it earlier. I've used that functionality myself before. On top of that, what they replaced the Samsung Android version with was a crippled, no hardware acceleration piece of crap. But I think they already knew that, and they knew exactly why that "backdoor" was there, but now their obscure "alternative" to stock installs is all over the nerd news.
Re: (Score:3)
That "obscure alternative" is one of the only ones consisting of entirely free software. Instead of whining that something doesn't work you should rather help implementing what's missing, either by direct contributions, money donations or even just a good word to the developers. Otherwise the rarity of free mobile systems like SHR, QtMoko or Replicant will become even more rare and none of them will be ever usable for anyone else than hardcore geeks.
Re: (Score:2)
Does Deckard Know this? (Score:3)
I'm sure Samsung is sending in the blade runner for these replicants hackers
Re: (Score:3)
They shouldn't need to expose full filesystem I/O for a remote wipe. They should only need to expose a locked up command that triggers the wipe within the local OS.
Either this is a back door, or they are the worst software engineers ever.
Comment removed (Score:4, Insightful)
Re: (Score:2)
Really? So what's the point of being able to read files belonging to the owner? If the backdoor only permitted nuking of the filesystem, then it wouldn't be a big deal. This is pretty clearly an application to facilitate surveillance of citizens, and therefore can be fairly described as sinister.
Re: (Score:2)
Why would a wipe my data function need the ability to read a file and transmit it over the modem? Why would it need a download this and save it here function?
Re:Who's behind that back-door ? (Score:4, Funny)
NSA ?
GCHQ ?
Or their equivalent from South Korea ?
AT&T
Re: (Score:2)
NSA ?
GCHQ ?
Or their equivalent from South Korea ?
AT&T
AT&T would be redundant for NSA.
Re: (Score:2)
Sorry but AT&T is far more evil than the NSA.
Re: Who's behind that back-door ? (Score:2)
Not really.
You pay AT&T to rape you. The NSA does it for free.
Re: (Score:2)
I'd provide a link to the NSA budget, alas that is classified [fas.org]. But rest assured that they are being paid, you can stop sending them your food stamps now.
Re: (Score:2)
Sorry but AT&T is far more evil than the NSA.
True. As another poster has observed, the NSA rapes you as part of your basic taxpayer services at no additional cost.
Plus, the NSA doesn't employ telemarketers to call you up 5 times a day 7 days a week year after year, exploiting the loopholes in the "Do Not Call" registry. To say nothing of the junk mail.
Re:Who's behind that back-door ? (Score:4, Insightful)
"Never attribute to malice that which can be attributed to stupidity."
My guess, after years of working with Samsung's poor-quality platform software and multiple runins with their utterly piss-poor configuration management processes (as in, the Korean divisions at Samsung Mobile don't seem to have any, as evidenced by numerous situations during the Superbrick fiasco):
Samsung probably put this into the RIL library to facilitate modem debugging. e.g. the modem can read/write to /efs/root/ in order to make it easier for a developer to track state changes of the modem or whatever. (Why do this instead of using whatever debugging functions are built into the modem such as maybe JTAG? This is probably for late-stage development where they wanted to test finishing touches on the modem using final hardware and the modem's debugging functions weren't physically available.)
Keep in mind that, based on the reverse engineering effort, Samsung *intended* this feature to only access files within /efs/root/ - the EFS partition is specifically reserved for device-specific state and calibration data (most notably the phone's IMEI is stored in the EFS partition, and with the exception of some miscellaneous other config data such as MAC addresses for wifi and BT, it's almost entirely for modem-related items. I may be wrong about the MAC data, I'm a bit rusty and haven't poked around at my EFS partitions in a long time.) It's only due to a screwup (lack of sanitization of escape sequences such as ../../ ) that someone can in theory access files outside of /efs/root
So at some point, Samsung probably removed the corresponding components on the baseband firmware side (no one has yet to confirm anything on the modem side that sends these commands, nor has anyone caught any of these commands being issued - the behavior of the library was verified by injecting extra commands with a kernel patch in the driver between the modem and the library), but someone forgot to remove them from the RIL library on the applications processor side. Forgetting to remove dead code and/or leaving epic security holes in place (remember that in late 2012, someone realized that Samsung left a world readable/writable device node that effectively mapped all system memory to that device file - allowing anyone to read or write any part of memory. For more, do a Google search for "exynos-abuse" ) is pretty typical for Samsung.
As to my experience here - I was one of the Cyanogenmod maintainers for the Exynos 4210 (I9100, I777, N7000) handset family, and also did some work on 4412 devices (primarily the Note 10.1 - GT-N8013) throughout 2012 and the first half of 2013. I'm 90% retired from working with Haxxinos these days and was (along with the majority of the rest of the Exynos maintainers) one of the people who left the project to start Omni after the Focal relicensing attempt fiasco.
An interesting question is - what architecture is the XMM626x's baseband processor? Is it custom or an ARM variant making it easier to analyze the baseband firmware itself? More than two years of working with that family of devices and I never personally looked in detail at what was running on the baseband side.
Re: (Score:2)
Another article on this, I agree with Dan's assessment - http://arstechnica.com/securit... [arstechnica.com]
Re: (Score:2)
You have obviously never worked closely with software written by Samsung before.
You know, the company that shipped millions of chips that would be damaged permanently if you send them a secure erase command. (Remember http://www.anandtech.com/show/... [anandtech.com] - What they don't tell you in that article is that Samsung shipped eMMC chips with the SAME EXACT BUG in every single international Galaxy S2 and Galaxy Note sold for many months.)
This is also the company that had a device file that was chmodded 666 or 777 th
Dupe (Score:5, Informative)
Yeah we know.
http://mobile.slashdot.org/sto... [slashdot.org]
Re: (Score:2)
isn't this article an evolution of the last one? The last one was all "holy shiitzors there's a back hole!" this one is all "fuzxors we fixed it for ya!"
Re: (Score:1)
No. It merely links directly to the FSF pos while the first one linked to other articles linking to the FSF post.
Re: (Score:1)
It's a Replicant article. Every time someone says the D word it Replicates itself.
Re:Dupe (Score:5, Insightful)
Replicant OS Developers Find Backdoor In Samsung Galaxy Devices
Replicant Hackers Find and Close Samsung Galaxy Back-door
Totally different story.
Re:Dupe (Score:5, Funny)
This story is a replicant...
Re: (Score:2)
Does anyone know if they are working on ... a pleasure model?
Wow! Two backdoors in one day? (Score:3, Funny)
Re: (Score:2)
Re: (Score:2)
First Post FAIL! (Score:1)
This article was already posted once before on slashdot today!
Slashdot editors (Score:3)
Slashdot editors fail to spot dupe, and fail to fix it - even though it's on the frikkin' home page. Wow, that really is news ;-)
Timothy, you've surpassed yourself. Tonight, when you go home to your SO and they ask you "how was your day, dear", you can proudly say "I really rocked today - I did some awesome stuff, I really moved the needle, I pushed the envelope, I really excelled!".
Re: (Score:1)
There's always this:
http://soylentnews.org/ [soylentnews.org]
Perhaps it'll free us from the laughable beta, and non-news for nerd clickbait too?
Re: (Score:2)
I have seen a dupe or two there. Still in two minds about whether it'll free us or dupe us... :P
Re: (Score:1)
I only discovered it very recently; competition is good, right? Not sure why it started exactly, but it's good to know that there's somewhere similar in case this one continues to get worse.
Re: (Score:2)
Worse? I would say you must be new here, but I can read useids... It was started by the whole "Fuck Beta" group which confused me (beta, was and as far as I know remains optional), and like all things borne of "violent" revolution suffers a bit from some infighting. Hopefully they'll resolve that, but it remains to be seen if they can build a decent community. I am registered and do read there, but comment more here, which says something.
Re: (Score:2)
Same here. I joined soylent and pipe, for good measure. For the time being though I still read /. more regularly and I haven't posted to either soylent or pipe so far. Soylent has already witnessed quite some drama (an ousted leader has used the phrase "palace revolt", I kid you not).
Re: (Score:2)
Timothy, you've surpassed yourself. Tonight, when you go home to your SO
There will already be another Timothy there.
oh for crying out loud timothy (Score:1)
Evidently the editors don't read the front page - given that there's *already* a story on there about this precise issue, using precisely the same blog.
Replicants? (Score:4, Funny)
Someone call Harrison Ford
Wow (Score:3)
I'm used to the dupes being weeks or months old... maybe Days for really bad ones. But this was like 12hrs ago? Do the editors even read slashdot anymore?
Re: (Score:1)
I think the better question is: Are the editors even functionally literate?
Re: (Score:2)
Yeah, see my UID? This has been happening for as long as I've been here. :)
Two words (Score:2)
Android
Re: (Score:2)
Either there is a whoosh sound, its under my threshold of hearing, or your counting skills suck.
I love the smell of dupes in the morning.... (Score:2)
Dupe? (Score:2)
In a word... (Score:2)
In a word: Yes.
The borderline (and sometimes not-so-borderline) criminal behavior of some software/hardware makers, coupled with often exorbitant costs for a device that will either be destroyed (via being cheaply made) or totally obsolete in a few years makes me quite leery of trusting or relying on a modern smartphone, much less actually spending my own money on one. Especially when my company provides me with a phone, POS though it may b
then Sailfish on Jolla phones? (Score:2)
But last I searched details on this, the actual progress and software availability was close to pathetic...