Member Avatar for MasterChat

Do we discuss this in this forum? If yes, how do we better protect ourselves? If no, it's ok.

  • 3 Contributors
  • 6 Replies
  • 252 Views
  • 4 Days Discussion Span
  • Latest Post Latest Post by Hiroshe

Dani AI

Generated

Useful context and a short action plan that builds on and : treat sensitive photos as a special case (minimize what goes to any cloud) and use a layered approach — provider-side protections where available, plus client-side encryption for anything extra-sensitive. (support.apple.com)

If staying with iCloud, Apple now offers an opt‑in Advanced Data Protection (end‑to‑end encryption) for many iCloud categories. It prevents Apple from decrypting protected items, but it requires two‑factor authentication, updated devices, and a recovery method (recovery contact or recovery key). Some sharing features (for example, certain shared albums or “anyone with the link” shares) are not covered, so enabling ADP reduces risk but is not a complete substitute for client-side control. (support.apple.com)

For hands‑on client control, encrypt before upload. On iOS use Cryptomator (creates an encrypted vault accessible via the Files app) so files stored in iCloud Drive are encrypted client-side; on desktops create an encrypted container or archive (VeraCrypt, encrypted ZIP/7‑Zip) and put that inside your cloud folder. Client-side encryption keeps the key with you and prevents server-side access — at the cost of extra steps and possible syncing quirks. (docs.cryptomator.org)

Practical checklist: turn off iCloud Photos or Shared Albums for private material, strip location/EXIF before sharing (Photos has an Options toggle), keep local encrypted backups (use Finder/iTunes encrypted backups or FileVault for Macs), enable strong Apple ID passwords and two‑factor authentication, and keep an offline recovery key or trusted recovery contact if you enable ADP. (support.apple.com)

This expands ’s caution and ’s client‑side idea into concrete options: choose provider E2EE when convenient, and add client-side encryption for anything you absolutely do not want exposed.

Recommended Answers

All 6 Replies

Member Avatar for Dani

Firstly, I would never put sensitive photos in the cloud to begin with. And if you did, make sure to encrypt them :)

Member Avatar for Hiroshe

Agreed. I would make sure that the client to the cloud has a built in symmetric cipher, where only the client (by extention, you) is able to reproduce the key, or I would make sure to encrypt them before transfer.

Member Avatar for MasterChat

I find it very interesting to read replies from learned programmers. It's way different from other people talking about the issue without programming background. How I wish I could relate soon enough.

Member Avatar for Hiroshe

If you like learning about privacy, Bruce Schneier has an excellent blog on the subject. He's as famous as Cryptographers come.

Member Avatar for MasterChat

Now that you mention cryptographers. Is it the same work they do with Dan Brown's Digital Fortress?

Member Avatar for Hiroshe

It's nothing like how it's portrayed in fiction. It's a feild of combinatorics and it's not quite that exciting.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.