"Defendant decided to destroy the contents of his device by providing CBP officers with a deletion code that wiped his phone." Given those facts, I would say the defendant didn't destroy anything. The officer destroyed it when she typed it into the phone.
Schneier long ago wrote about this. Travel with a clean phone/notebook. And once you are at your destination download from the net what's needed to do your work.
No need to flex because, as we can see, you get in trouble.
I really wish Android had a simple way to backup a phone in the same vein as Time Machine on MacOS and (icloud) backups on iOS can. That way you'd be able to restore from backup at your destination without issue.
I'm sure this is feasible with adb in an ideal world, but it never seems to quite work out like that.
You can't do it with adb. Android lets apps disable adb backup, and tons of apps do it, to the point it's basically pointless.
It's basically impossible, as the owner of your phone, to back up the data on it, except of course by logging into Google and letting them sync it to the cloud to leer at at their leisure.
Hmm years ago when I routinely wanted to have root on my phone, the first step was to install Clockworkmod in the recovery partition. This partition is supposed to have the utility that just flashes OS updates to the main partition, but Clockworkmod offers many other things, including partition backups as dd images. Doing that seems to be the simplest way of having 1:1 backups.
I really don't understand why there are no real choices for system level backup (ie; SeedVault, different to say Neo backup which is just delightful) - SeedVault is fine but: mnemonics are annoying and there is no remote backup. I'd really like something simple that does the same as Google/SeedVault system backup, but: encrypts with a passphrase of my choice (or uses PKI, or FIDO, or something more convenient), and can archive the backup to my destination of choice automatically. Not asking much here, I don't think...
Overall though, Android is obviously not modular, it isn't designed to be, but it would be really nice if user choices could be properly integrated into an image, even if I have to build it myself. At some point, people need to get together and fork Android rather than trying to maintain compatibility with what is a commercial platform with entirely disparate goals.
On the other hand, mobile devices should be ephemeral - so I try and keep mine that way, the few apps I actually use (fairemail, immich etc) can be restored properly with the "private" data using neo backup, but it's really not ideal. Just device and app configuration would be a good start, it need not backup the entire device and its contents as that is typically a duplicated operation since immich, email, etc, is already stored somewhere other than the device.
I think/hope the evidence will be suppressed since the CBP lied as to why they wanted to search the phone (child porn as opposed to terrorism). If it does, then I don't think we will get clarity on whether duress codes are illegal.
"Defendant decided to destroy the contents of his device by providing CBP officers with a deletion code that wiped his phone." Given those facts, I would say the defendant didn't destroy anything. The officer destroyed it when she typed it into the phone.
Is there a way to have it wipe your phone but present a useable fake instance of the account?
This logic would also be very comforting for landmine collectors.
But alternatively, the defendant sent a kill-code to the phone via CBP-finger-to-screen communication protocol.
Schneier long ago wrote about this. Travel with a clean phone/notebook. And once you are at your destination download from the net what's needed to do your work.
No need to flex because, as we can see, you get in trouble.
I really wish Android had a simple way to backup a phone in the same vein as Time Machine on MacOS and (icloud) backups on iOS can. That way you'd be able to restore from backup at your destination without issue.
I'm sure this is feasible with adb in an ideal world, but it never seems to quite work out like that.
You can't do it with adb. Android lets apps disable adb backup, and tons of apps do it, to the point it's basically pointless.
It's basically impossible, as the owner of your phone, to back up the data on it, except of course by logging into Google and letting them sync it to the cloud to leer at at their leisure.
Hmm years ago when I routinely wanted to have root on my phone, the first step was to install Clockworkmod in the recovery partition. This partition is supposed to have the utility that just flashes OS updates to the main partition, but Clockworkmod offers many other things, including partition backups as dd images. Doing that seems to be the simplest way of having 1:1 backups.
Clockworkmod hasn't been updated in over 10 years.
LineageOS backups via SeedVault are pretty good. https://github.com/LineageOS/android_packages_apps_Seedvault Not perfect, but pretty good!
I really don't understand why there are no real choices for system level backup (ie; SeedVault, different to say Neo backup which is just delightful) - SeedVault is fine but: mnemonics are annoying and there is no remote backup. I'd really like something simple that does the same as Google/SeedVault system backup, but: encrypts with a passphrase of my choice (or uses PKI, or FIDO, or something more convenient), and can archive the backup to my destination of choice automatically. Not asking much here, I don't think...
Overall though, Android is obviously not modular, it isn't designed to be, but it would be really nice if user choices could be properly integrated into an image, even if I have to build it myself. At some point, people need to get together and fork Android rather than trying to maintain compatibility with what is a commercial platform with entirely disparate goals.
On the other hand, mobile devices should be ephemeral - so I try and keep mine that way, the few apps I actually use (fairemail, immich etc) can be restored properly with the "private" data using neo backup, but it's really not ideal. Just device and app configuration would be a good start, it need not backup the entire device and its contents as that is typically a duplicated operation since immich, email, etc, is already stored somewhere other than the device.
Even iOS does not backup faithfully. You still need to do chores when restoring like reauthenticating to multiple apps. It’s a pain.
That's not been my experience, but then again, I don't have many apps to reauthenticate to, and am about 3 years out of date on this front anyway.
99.9% of people don't need to do this. But yes, if the hat fits, wear it.
I think/hope the evidence will be suppressed since the CBP lied as to why they wanted to search the phone (child porn as opposed to terrorism). If it does, then I don't think we will get clarity on whether duress codes are illegal.
Musk-free link: https://xxcancel.com/GrapheneOS/status/2124155903729639818