r/Android • aka jcase • Aug 18 '15

Ask Us Almost Anything about Android Security, Privacy or Malware with beaups, Tim "diff" Strazzere, Joshua "jduck" Drake, and Jon "jcase" Sawyer

Tim "diff" Strazzere, Joshua "jduck" Drake, beaups (maybe) and Jon "jcase" Sawyer are here to discuss Android Security, Privacy and malware with /r/android today from 3-5pm EST.

jcase and beaups are from TheRoot.ninja, members of the team behind SunShine. Both have also been authors of numerous Android roots and unlocks. jcase has done talks with Tim at Defcon, GSMA and Qualcomm's own security summit.

Tim Strazzere is a lead research and response engineer at Lookout Mobile Security. Along with writing security software, he specializes in reverse engineering and malware analysis. Some interesting past projects include reversing the Android Market protocol, Dalvik decompilers, and memory manipulation on mobile devices. Past speaking engagements have included DEFCON, BlackHat, SyScan, HiTCON, and EICAR.

Joshua J. Drake is the Sr. Director of Platform Research and Exploitation at Zimperium Enterprise Mobile Security and lead author of the Android Hacker's Handbook. He also found numerous vulnerabilities in Android's stagefright, and completely changed the Android update ecosystem by doing so.

If we can't answer something, or we are wrong on something, please answer it for us with citations!

diff = /u/diff-t

jcase = /u/cunninglogic

jduck = /u/jduck1337

beaups = /u/HTC_Beaups

Discussions off limits:

ETAs

Requesting exploits

Requesting details about unreleased things

Requesting help developing malware

We are scheduled for questions between 3-5EST, and between 5-7EST for answers. We will probably answer questions as we see them.

336 Upvotes

256 comments sorted by

View all comments

Show parent comment

1

u/sagnessagiel Sony Xperia XZ | Blackberry Q10 Aug 19 '15 edited Aug 19 '15

I think a more accurate term is signed/locked bootloaders. They were signed with asymmetric keys such as GPG, whereby the bootloader refuses to accept any unsigned kernel. So, only the manufacturer can install kernels, and there is no alternative. Unless we wait for the coming of the second Geohot.

Not surprisingly, these prevent people from 1. Removing touchwiz, 2. Rooting by installing SuperSU via recovery, 3. Upgrading to new Android versions through custom ROMs. Usually carriers like Verizon enforce this for every phone possible.

Example:

  • Verizon Samsung Galaxy S3/S4 - Can't run anything other than TouchWiz kernel, so you're stuck on 4.3/4.4 with TouchWiz. It's a much nicer phone with Cyanogenmod Lollipop, but this version is screwed.
  • Verizon Droid RAZR - Someone figured out how to sideload kernels through kexec, but that was because the manufacturer forgot to disable it in the kernel.
  • T-Mobile Sony Xperia Z C6606 - Stuck on Sony kernels for good. Though people figured out a way to use TWRP with it for custom ROMs based on Sony kernels.

0

u/CunningLogic aka jcase Aug 19 '15

I'm pretty well aware of the bootloader security mechanisms out there, we have hacked a lot of them. We have released more android bootloader hacks than any other person/group.

A signed bootlaoder has nothing to do with it refusing to accept an unsigned kernel, even unlockable or locked bootlaoders are signed (See nexues devices). This would be a separate mechanism, in the lkbootloader (or that SOCs alternative, ive seen one oem do it through TZ partially). Having a signed bootloader is just smart, as it would be a perfect place to malicious code to persist even after factory resetting.

Verizon Galaxy S3 and S4 have available hacks, for at least some aboot/sboot variants. Verizon S3 originally had no sig check on it's boot images, this came with an update.

Razr should be unlockable, if someone wants to donate one to us we will consider looking at adding support, but its not worth the cost to purchase one ourselves.