> 1) Maybe I know what I'm doing (honestly .. I consider myself capable and still have cringe while writing this) My example kinda covers this, phones really a

> 1) Maybe I know what I'm doing (honestly .. I consider myself capable and still have cringe while writing this) My example kinda covers this, phones really are getting faster... It's no longer a case of "I know what I'm doing" when it now comes down to human recognition and reaction time. In other words, you clicked allow before your brain had time to stop you. How do you prevent this? > 2) Your software isn't immediately compromised in its core functionality if _I_ own my _own_ device. 100% agreed. For the Google Pay example, fair enough. It's your credit cards, and it's harder to come up with a counter point.. For the OP / Netfix example, it's not your data, and likely not your device - or - by connecting to company services, you've basically agreed it's not yours (This could be a whole sidetrack on it's own! :)) > Android Pay and whatever else might try to be your wallet (I'm a huge fan, as you might notice in this thread) should be able to withstand that. Otherwise it's just a crappy payment system. Credit card companies are generally responsible for theft of money where you remained in possession of your card at all times. Sure, they really hate admitting it, and gathering the proof is hard, many times impossible. But that doesn't change the responsible party when the proof is found.. Given this, it's easier for them to accept less secure alternatives (e.g. the US's reliance on signatures). The rise of NFC credit cards has changed this somewhat, if a credit card hands out all the details needed to make a purchase to anyone who bumps into you on the street, possession is now not the only factor, and banks have built safeguards around this (e.g. max transaction size, max NFC transactions before being required to enter your PIN). Google with Android Pay must prevent that same bump on the street from stealing their customers money. The cell phone payment version of this comes in the form of other apps on the device, hackers breaking into the phone remotely, etc. With a rooted device, or a device using unknown firmware[1], all bets are off. > I can pay stuff from my PC (various operating systems) and I do have root (or the equivalent permissions). And this is a security hole, granted it's one I wouldn't want to see shutdown, but it's still security hole. I don't have any good answers here, but I do look forward to seeing a solution that works while letting me keep root access on my Linux box! > Why is the CC secure, but a rooted phone isn't. I'm think I've mostly covered this, but you're looking at two totally different landscapes. They just cant be compared in the same way. > Ignore Netflix, they're brain-dead and content related DRM isn't what I'm going for. While I'm no DRM fan, this entire article is about Netflix's corporate employee device security, it's nothing to do with DRM or content.. [1]: Unknown firmware in this case means firmware google doesn't trust - unrooted AOSP built from a unknown manufacturer can't be trusted any more than rooted firmware from Google itself.