News for hackers. Stuff that matters.
Re:Bugs in our pockets: the risks of client-side scanning by perihelions on Tuesday October 26, 2021 @05:40PM (#29006673)
But none of these conundrums could exist if Apple had no access to the user's device, nor control over the software running on it. "Who owns your computer" is still the central question; we're just Sapir-Whorfing ourselves around it within the implicit language of walled gardens. "Apple owns your computer" is the unspoken premise, and it's not axiomatic.

Stallman was very, very right.

Re:Bugs in our pockets: the risks of client-side scanning by aidenn0 on Tuesday October 26, 2021 @06:27PM (#29007176)
There's a huge tangle of things with "Apple owns your computer" but I don't think most of it applies to the icloud question.

If you wanted to store photos in icloud on a Windows machine, you'd be using the Apple icloud client. Apple has at least some control over what software they write and ship does[1]. They can break 3rd party clients almost at will, so if they choose to be hostile to 3rd party clients that control is fairly strong.

Arguing over what amount of control Apple should exercise over what software runs on a device purchased by a consumer is mostly orthogonal to arguing over what amount of control Apple should exercise over what software can connect to their servers.

1: On a general purpose machine, debuggers and emulators can influence what software does, obviously, so the control isn't absolute.

Re:Bugs in our pockets: the risks of client-side scanning by someguydave on Wednesday October 27, 2021 @01:55AM (#29009998)
It seems to me that Apple does their best to ensure you end up using icloud against your will through a a series of very confusing opt-out prompts and defaults.

Maybe it would be nice to have a tool that would allow you to see exactly what data the client side scanner is “allowed” to “see”?

Re:Bugs in our pockets: the risks of client-side scanning by mro_name on Wednesday October 27, 2021 @02:18AM (#29010089)
… or have regulation that enforces such.
Re:Bugs in our pockets: the risks of client-side scanning by Dylan16807 on Wednesday October 27, 2021 @01:37AM (#29009906)
Well services generally shouldn't be controlling what software can connect either!

The argument over whose computer it is applies pretty similarly. My computer is not part of their infrastructure, and they should only be controlling the software on their infrastructure.

Re:Bugs in our pockets: the risks of client-side scanning by tshaddox on Tuesday October 26, 2021 @09:55PM (#29008751)
Apple develops a phone operating system and sells phones that run that operating system. What does it even mean to say “if Apple had no access to the user’s device”?
Re:Bugs in our pockets: the risks of client-side scanning by perihelions on Tuesday October 26, 2021 @11:36PM (#29009278)
Yes, Apple is also the OS vendor. What it would mean to say "Apple has no access to the user's device" is, whatever an average, unsophisticated user understands it to mean -- because their informed consent is ethically all that matters here.

It means precisely that Apple has no technical capability to remotely access the device.

It means any (consented) Apple software update leaves behind no hooks or backdoors that enable subsequent, remotely-initiated access.

It means there verifiably exist no code paths that allow remote exfiltration of data, other than those that pass through consent dialogs. The basic distinction between legitimate OS functionality, and malware.

Re:Bugs in our pockets: the risks of client-side scanning by tshaddox on Tuesday October 26, 2021 @11:55PM (#29009373)
But average users are clearly aware of many high profile iPhone features that inherently involve Apple “remotely accessing the device,” assuming you're include all cases where the iPhone software can be configured to send data from the device to Apple servers. That’s what all iCloud services explicitly do.
Re:Bugs in our pockets: the risks of client-side scanning by perihelions on Tuesday October 26, 2021 @11:57PM (#29009383)
Yes, but the distinction between "stores private data E2E encrypted on a secure server" and "uploads private data for Apple employees to review" is a bright line. Informed consent means we can't extrapolate from one to the other, if we pretend to be ethical.

It's not as if Apple's marketing doesn't heavily emphasize the "private", "E2E encrypted" aspects already.

Re:Bugs in our pockets: the risks of client-side scanning by mro_name on Wednesday October 27, 2021 @02:24AM (#29010114)
yes, consumers want to - well - consume. And not be bothered with anything other than that.

So somebody else has to do housekeeping and hand-holding. That's where apple comes in again, or better, stays for convenience sake.

And to not complicate their own day, Apple just does it the same for all.