Hacker News new | past | comments | ask | show | jobs | submit login

Change the name of your iPhone. The default name may include your actual name, which can be seen in more places than you'd think.

Wipe/reset your iPhone every now and then. There is residual data left on the phone from app/data deletion (left over databases even). A factory reset will clear this, OS updates can help as well. The "Other" section of your iPhone storage is dangerous.

Make sure the emergency feature to disable TouchID/FaceID is enabled. When turned on it kills biometrics until you put in your (hopefully unique and complex) password. Otherwise, biometrics is safer.

Don't add any mail accounts to the native iOS mail app.

Ensure that access to USB accessories while the phone is locked is turned off.

Work only on LTE and your own private Wi-Fi (your job will have very complex monitoring tools like FireEye). Disable cellular data on any apps that you won't actively be using.

Backup your iPhone to a secure location when travelling, wipe your phone and then re-build your phone using the backup upon arrival. Destroy the backup after.

Don't open any shady URLs and make sure you always update iOS. Turn on auto-update.

Security is critical on iOS as some apps have the ability to log you in or restore a session without any sort of credential check. This is despite the fact that unique device identifiers are not supposed to be used by devs.

Protect yourselves!




>> Backup your iPhone to a secure location when travelling, wipe your phone and then re-build your phone using the backup upon arrival. Destroy the backup after.

Do you think better it’s is better to have an interim account after reset the phone and before rebuild the phone with the backup?


> Security is critical on iOS as some apps have the ability to log you in or restore a session without any sort of credential check. This is despite the fact that unique device identifiers are not supposed to be used by devs.

I've noticed this before. How is that possible?


Some apps with persistent "anonymous" logins save an identifier to the keychain and sync it with iCloud so that it persists between installations and across devices.



OAuth2 token authentication?


> Don't add any mail accounts to the native iOS mail app.

Woah, I haven't heard this advice before—is the argument that the native mail app is less sandboxed than an App Store app? If so that makes a lot of sense (especially given P0's recent exploit chain involving an IMAP client vulnerability), sigh.


MDM related APIs change so often I just tell people to assume that all the native apps are less sandboxed.

Another thing you can do is to download apps using one Apple ID, then login again to the App Store with a different Apple ID.

The tricky thing about iOS is things are always changing, so precautions that might seem fruitless today may be critical tomorrow.


I'm not sure I follow - what potential changes would this defend against?


Any recommendations for non-Apple iOS IMAP client app, which does all processing locally?


Canary Mail [1] comes to mind. They also offer PGP encryption support.

[1] https://canarymail.io/


Thank you!




Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: