On Mon, Jan 28, 2013 at 5:17 PM, jduck <[email protected]> wrote: > I recommend getting him his own device. He's less likely to want yours > then. My little one slobbered devices to death in the past. It's only a > matter of time before a phone ends up in the toilet. Whether its an iOS or > Android device makes little difference to the throne. > Hahahaha ;> My friend has his baby's iPhone 3G inside some sort of plastic play toy that looks like any other baby toy. The plastic toy looks kid-proof and toilet-proof. It's a big hunk of brightly-colored plastic tube-shaped handholds with a giant white center hard, thick plastic case. I have no idea where he got it.
> I really doubt you're gonna be able to get this feature disabled. Your > work most likely requires this as a condition of you having work email on > the device. That and they probably require you to let them remote wipe it > whenever they want. Just food for thought... > They'll have about enough time to remote wipe a device as I have to forensically acquire its memory (and later, usually while powered off, its disk). I hope that they can detect that I'm doing that and respond in that window of time. How many hours would it take for an adversary to re-purpose some sort of shim that blocks unwanted behavior on part of the MDM (such as remote wipes) and that allow wanted behavior (such as allowing work email to send/receive)? Didn't we already do this in the NAC days of information/application/data security? Didn't that fail pretty sadly, gaining nearly no momentum or traction for years and then eventually dying off and turning somewhat into SIEM? dre -- You received this message because you are subscribed to the Google Groups "Android Security Discussions" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/android-security-discuss?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
