News for hackers. Stuff that matters.
Re:Bugs in our pockets: the risks of client-side scanning by dylan604 on Tuesday October 26, 2021 @05:22PM (#29006446)
Client side scanning of inappropriate pictures is of content you'd ordinarily be sending them as anyways as well. The proposal was only to do this if cloud services were/are enabled.
Re:Bugs in our pockets: the risks of client-side scanning by inetknght on Tuesday October 26, 2021 @05:58PM (#29006871)
> Client side scanning of inappropriate pictures is of content you'd ordinarily be sending them as anyways as well. The proposal was only to do this if cloud services were/are enabled.

I have an iPhone. The Photos app keeps telling me that it's unable to upload things to iCloud because my account is full.

I never turned it on. I never intended to upload any photos to the cloud.

I haven't signed into my iCloud account for years because I don't use it. Nonetheless, iCloud has a magical way of uploading things to something that I've literally never used.

Next you'll be arguing that people using Windows should have simply turned off online logins if they didn't want their Windows computer to phone home. Bullshit, Microsoft shoves that shit down people's throats.

So your statement of "you'd ordinarily be sending them as anyways as well" is ludicrous. That's deliberately burying your head into he sand against the fact that big business sets defaults to settings that users often have no idea were set or are buried behind huge warnings against turning them off.

Re:Bugs in our pockets: the risks of client-side scanning by nitrogen on Tuesday October 26, 2021 @06:45PM (#29007340)
Bullshit, Microsoft shoves that shit down people's throats.

As an example of this, I never once opted into any kind of data sharing, set telemetry to the lowest allowed setting, and don't remember ever signing into a system-wide Microsoft account, yet when I eventually discovered deeply hidden privacy options I found that my MS account had a log of every single application I had ever used on my W10 laptop.

Re:Bugs in our pockets: the risks of client-side scanning by jodrellblank on Tuesday October 26, 2021 @08:54PM (#29008387)
Where the "deeply hidden" options under Settings -> Privacy -> Activity History with "Jump back into what you were doing on your device by storing your activity history"?

It implements the feature of pressing Win+Tab to see open programs, and then scrolling down to see previously open programs.

Re:Bugs in our pockets: the risks of client-side scanning by GekkePrutser on Tuesday October 26, 2021 @07:12PM (#29007585)
Really?? Where do you find this? I'd like to document this for myself in case I end up in a discussion about such matters.
Re:Bugs in our pockets: the risks of client-side scanning by nitrogen on Wednesday October 27, 2021 @03:17AM (#29010424)
I found the data somewhere in the MS account profile page.
Re:Bugs in our pockets: the risks of client-side scanning by GekkePrutser on Tuesday October 26, 2021 @07:11PM (#29007577)
Sadly, Windows phones home just the same if you have a local account.

Now I get that they need to check that I have a valid license. Fair enough. Anything beyond that should be opt-in.

Re:Bugs in our pockets: the risks of client-side scanning by dylan604 on Tuesday October 26, 2021 @06:04PM (#29006930)
I've had an iDevice since 2007. I've never signed up for the paid iCloud. I get the standard 5GB plan that all Apple accounts receive. I have never accidentally uploaded a photo to it. I have never enabled it. I don't understand how your situation happens as it has never happened to me. It makes no sense other than someone (maybe you forgot, a significant other, a kid) played around with some settings? There's no other explanation that makes sense to me.
Re:Bugs in our pockets: the risks of client-side scanning by inetknght on Tuesday October 26, 2021 @06:17PM (#29007063)
There's nothing better than knowing everything and never having to play around with settings to discover what they do, never forgetting what you've set your settings to, and not having children, family members, or friends do the same. There's no way any reasonable person could ever have their uploads accidentally turned on without their full knowledge and consent so that definitely invalidates any reason to argue against the idea that client-side scanning is unreasonable because it only happens to things that you wanted to upload anyway.

There's definitely no way a new version could patch your system and turn something on without your knowledge. No, there's absolutely never been a situation where some new setting has shown up and you didn't know what it does or inspected what it was set to by default. And there's absolutely no way you could have restored a backup and not had all of your settings transfer over correctly. No, there's no way you'll ever turn the setting on and forget that it's on when you plug your device into some network. And you know you will never be the victim of any malicious activity that could screw you over in some way. You've never had some app automatically connect to something that you didn't know it could even connect to. You'll never have someone else pick up your phone and take random pictures or recordings that you don't know about because those would never get automatically uploaded because, of course, you didn't turn on that setting for yourself. You'll never have to worry about your battery going low because you turned on automatic uploads and not only did your upload happen but your device also scanned your uploads too. You never use your phone for work because your work definitely pays for a new device for you to use for work.

Gosh it sure is weird hat so many people don't want client-side scanning. Scanning your device before uploading anything is just a very reasonable thing to do.

/s

Re:Bugs in our pockets: the risks of client-side scanning by dylan604 on Tuesday October 26, 2021 @06:52PM (#29007413)
I don't want client side scanning, and I don't want the cloud. If only wishing made it so.

People not being able to understand the devices they use is why devs have gotten us to this point. People are too uneducated to do proper back ups, so some enterprising people came up with a way to do that for you. Peeps still get it wrong. Some other asshats come along and take advantage of uneducated people, and do malicious stuff. Fuck 'em. We should just end the cloud because we as a society can't handle it or the responsibility of operating our own equipment. /s

Re:Bugs in our pockets: the risks of client-side scanning by jodrellblank on Tuesday October 26, 2021 @10:38PM (#29008995)
With server side scanning, if someone accidentally enables uploading you are in exactly the same position. It being enabled on upload, which side it runs changes nothing in all the scenarios you are sarcastically ranting about.
Re:Bugs in our pockets: the risks of client-side scanning by inetknght on Wednesday October 27, 2021 @12:39AM (#29009608)
> It being enabled on upload, which side it runs changes nothing in all the scenarios you are sarcastically ranting about.

You're wrong because at the very minimum it means that my device's battery isn't consumed for the scanning.

Further, enabling uploading won't work if the cloud account is full (as is currently the case).

Turning off connectivity prevents the upload and scanning from occurring.

Re:Bugs in our pockets: the risks of client-side scanning by jodrellblank on Wednesday October 27, 2021 @04:59PM (#29019042)
> Further, enabling uploading won't work if the cloud account is full (as is currently the case).

> Turning off connectivity prevents the upload and scanning from occurring.

Client side scanning which happens as part of the upload, so these apply to that as well as to server-side scanning.

So your complaint is only "battery life"?

Re:Bugs in our pockets: the risks of client-side scanning by inetknght on Wednesday October 27, 2021 @08:15PM (#29020793)
> So your complaint is only "battery life"?

No. Way to miss the forest for the trees. Go read the whole thread.

Re:Bugs in our pockets: the risks of client-side scanning by jodrellblank on Thursday October 28, 2021 @12:29AM (#29022397)
OK, I've re-read your complaints about client-side scanning which also apply equally to server-side scanning in every way except battery life, and I've noticed you also incorrectly frame "scanning your device before uploading anything" which it doesn't do, it scans only the things being uploaded not the whole device and as part of the upload.

You either misunderstand it or are deliberately being misleading about it. The only complaint that you have made which stands is battery-life.

Re:Bugs in our pockets: the risks of client-side scanning by haswell on Tuesday October 26, 2021 @06:19PM (#29007086)
> since 2007

I'm speculating here, but I wonder if part of your experience is based on the fact that you're a long time user. Features like auto-uploading to Photo Library are new, and Apple is generally decent about informing you of new features before opting in.

Brand new account setups are a different story. You're encouraged to use all of the latest/greatest stuff (and why not, current topic notwithstanding?).

Bottom line: it's extremely easy for an average user to start uploading their stuff without really realizing it.

Re:Bugs in our pockets: the risks of client-side scanning by dylan604 on Tuesday October 26, 2021 @06:47PM (#29007370)
Maybe. I'm very anti-cloud from the first moments I ever heard of it and saw the first puffy shapes in slide decks. I don't trust it. It's not in my control and I don't know who does control it. That scares the bejeebus out of me.

I'm not the unsuspecting dupe that devs are targeting to get a new user tricked into something. I'm very much aware of the shenanigans devs try and pay attention to that shit from the go.

Having said that, I do read the crap and choose no where necessary. People just haphazardly pressing okay to get to new shiny almost deserve whatever they've agreed to. I say almost because these dialogs can be worded like "Vote No for Yes" kind of BS.

If you're one of the asshat devs FUCK YOU for making this a thing we even have to discuss in the first place. Edit: Royal You Devs

Re:Bugs in our pockets: the risks of client-side scanning by GekkePrutser on Tuesday October 26, 2021 @07:14PM (#29007610)
It's not even the devs in general. It's their management and bean counters. Data is money.

And yeah.. The cloud is just someone else's computer. Would you store all your stuff on your friend's computer? Well most people store everything they have on the computers of people they don't even know...

Re:Bugs in our pockets: the risks of client-side scanning by dylan604 on Tuesday October 26, 2021 @07:27PM (#29007732)
Thank gawd we don't make decisions on what most people do...hrmph
Re:Bugs in our pockets: the risks of client-side scanning by haswell on Tuesday October 26, 2021 @05:32PM (#29006557)
A significant number of concerns aren't about the feature as proposed by Apple, but the slippery slope it creates.
Re:Bugs in our pockets: the risks of client-side scanning by fsflover on Tuesday October 26, 2021 @05:53PM (#29006802)
More about this slippery slope: https://news.ycombinator.com/item?id=28309202.
Re:Bugs in our pockets: the risks of client-side scanning by GekkePrutser on Tuesday October 26, 2021 @07:19PM (#29007654)
True but slippery slopes are simply a thing. Like the Overton window. Every move takes a step further and moves something else from ridiculous into feasible.

And personally, I know this won't affect me. I don't own such content. I don't use the cloud without encryption first (thanks Cryptomator). However I just hate the feeling of my own phone constantly looking over my shoulder on someone else's behalf. Is that so weird?

Re:Bugs in our pockets: the risks of client-side scanning by haswell on Wednesday October 27, 2021 @12:09PM (#29015195)
I think we're saying the same thing. 100% agree here. I think (hope) the vast majority of folks wouldn't be affected by the proposal. But the backlash against it has been justified for exactly the reasons you outline.