News for hackers. Stuff that matters.
Re:Android: I don't need your permission by nly on Tuesday December 16, 2014 @04:50PM (#8759786)
In practice you can disassemble Java apps to pseudo source code anyway. I've done it several times to APKs to see what is going on under the covers. Deliberate obfuscation would be immediately suspicious.
Re:Android: I don't need your permission by stusmall on Tuesday December 16, 2014 @05:48PM (#8760078)
I wouldn't say that. Obfuscation isn't that rare in Android. Proguard offers tree shaking and optimization features that are useful in mobile. Some frameworks even require it. AFAIK most set ups for scala on android need proguard because the standard lib is so big.
Re:Android: I don't need your permission by acdha on Tuesday December 16, 2014 @05:15PM (#8759926)
1. How closely would you have to look to notice something like a weak crypto setup or other “accidental” change less obvious than sending everything to “all-your-bytes.nsa.gov”?

2. How many people other than blackhats actually have the time to do this for every single automatic update?

Re:Android: I don't need your permission by kuschku on Wednesday December 17, 2014 @12:07PM (#8763064)
It’s actually really easy.

I tried understanding the APIs several phone apps are using, (the apps are heavily obfuscated), so I decompiled them and hacked my own small deobfuscater where I could rename stuff half-automatically.

Then I went through the code of Google Apps with this, and it’s actually really nice. Although kinda surprising how many Google Apps have hardcoded API keys for their services floating around, for example there is one Google App which has a hardcoded key that allows full unthrottled API access to all of the Google Maps APIs. For free.

I just did this out of fun, as I’m mostly working on Android OpenSource apps, but it was quite easy and interesting to see how Google obfuscates their apps.

Re:Android: I don't need your permission by acdha on Wednesday December 17, 2014 @02:20PM (#8763782)
Finding predictable things like hard-coded strings is a significantly easier task than proving that none of the code is doing something sneaky. It's much easier to look for something like an access key than confirm that the numeric constants being passed to a crypto function are the correct ones or that it's not leaking something which would make it much easier to crack.
Re:Android: I don't need your permission by kuschku on Wednesday December 17, 2014 @03:36PM (#8764196)
We’re not talking about hardcoded strings, lol.

This is encryption and obfuscation on multiple levels, classes passing each others state through hashing and encryption schemes on multiple levels, added bytecode hackery, etc.

Re:Android: I don't need your permission by acdha on Thursday December 18, 2014 @08:08AM (#8767058)
Exactly my point – it's unreasonable to expect that higher level of reverse engineering will be done reliably for every release of even a small percentage of the apps being published.
Re:Android: I don't need your permission by micampe on Tuesday December 16, 2014 @05:01PM (#8759856)
You say obfuscation I say compression.
Re:Android: I don't need your permission by marvy on Tuesday December 16, 2014 @05:34PM (#8760016)
good one!
Re:Android: I don't need your permission by Someone1234 on Tuesday December 16, 2014 @06:09PM (#8760173)
That's true. But if you leave automatic updates enabled then the whole exercise is nearly pointless.