News for hackers. Stuff that matters.
Re:Apple to kill Epic’s accounts on Friday the 28th by ryandrake on Monday August 17, 2020 @05:57PM (#24192684)
An application that suddenly changes behavior due to no action taken by the user, triggered remotely by the developer, is getting very close to the "malware" line in my book.
Re:Apple to kill Epic’s accounts on Friday the 28th by CobrastanJorji on Monday August 17, 2020 @06:59PM (#24193292)
A one day 10% off sale is a change in behavior due to no action taken by the user triggered remotely by the developer. Is a sale very close to malware?
Re:Apple to kill Epic’s accounts on Friday the 28th by jachee on Monday August 17, 2020 @07:26PM (#24193499)
Depends.

Does the sale require me to submit payment details to a not-already-trusted platform?

The change remotely triggered by Epic redirects users to a third-party (Epic) payment system, but what if it were, say, a malicious Epic insider? How much user payment info/cash could they grab before they were detected and disabled?

Re:Apple to kill Epic’s accounts on Friday the 28th by tfigment on Monday August 17, 2020 @11:05PM (#24194838)
They actually gave 2 options. If you didnt trust the game maker and their discount you could continue paying the premium to Apple directly and continue feeling safe.
Re:Apple to kill Epic’s accounts on Friday the 28th by AlexandrB on Monday August 17, 2020 @11:56PM (#24195103)
It's funny that this choice wasn't "offered" to console users who got the 20% discount even as 30% still went to Sony/Microsoft. The two-tier pricing on iOS was purely a stunt and had nothing to do with Epic's costs.
Re:Apple to kill Epic’s accounts on Friday the 28th by axlee on Monday August 17, 2020 @06:19PM (#24192908)
Any automatic software is a malware, according to that definition. That's weak.
Re:Apple to kill Epic’s accounts on Friday the 28th by tdrp on Monday August 17, 2020 @07:53PM (#24193684)
Seriously. We generally release most of our new features at 10% of the users and then gradually increase the percentage on the server end. If there's any issue we can turn it off immediately rather than potentially waiting days for the app store to approve our fix.
Re:Apple to kill Epic’s accounts on Friday the 28th by ryandrake on Monday August 17, 2020 @10:14PM (#24194598)
The use of feature flags to show/hide features is arguably against the App Store guidelines [1]:

"2.3.1 Don’t include any hidden or undocumented features in your app; your app’s functionality should be clear to end-users and App Review."

1: https://developer.apple.com/app-store/review/guidelines/

Re:Apple to kill Epic’s accounts on Friday the 28th by noodle on Monday August 17, 2020 @06:25PM (#24192965)
This is a pretty broad brush. It puts a lot of installable desktop or mobile apps into that bucket due to things like code push. And of course every web app falls in this territory.
Re:Apple to kill Epic’s accounts on Friday the 28th by floatingatoll on Monday August 17, 2020 @06:44PM (#24193139)
What is the definition of sufficient when it comes to protecting non-technical users from harmful code?

In old sci-fi books, there's a couple that describe a future where connecting an old device to the Internet without having first installed updates will result in the device being exploited and/or ruined within a few seconds.

I notice that the Xcode worm was reposted again this morning, which seems like the perfect mechanism for covertly preparing for a worldwide hack of all iOS devices through a backdoor that has been compiled into all software. (You could get a similar effect by introducing malware into CocoaPods, and with similar reach.) All of these protections Apple has with Gatekeeper and Notarization would, to many extents, protect end users against that attack.

As you said, it's definitely a broad brush. The risk is absolutely real, though I imagine we all disagree on how important it is. It's the same problem as the risk of Python/Ruby/Node dependency compromises. Any solution that would work for protecting us against an NPM compromise would also work for protecting us against a macOS software compromise. Apple's solutions have a higher total value of protection, in exchange for a higher total value of bothersome.

Is the NPM model (you can ship any code worldwide, have fun!) safe enough for non-technical users, such that Apple could just drop Gatekeeper and let us all go back to the wild west macOS days? If not, what model is acceptable, given that Apple's model isn't?

Re:Apple to kill Epic’s accounts on Friday the 28th by jonny_eh on Monday August 17, 2020 @06:04PM (#24192757)
It greatly depends on what that new behaviour is for it to be considered malicious.
Re:Apple to kill Epic’s accounts on Friday the 28th by nathansoz on Monday August 17, 2020 @08:07PM (#24193780)
A feature flag. You're describing feature flags.
Re:Apple to kill Epic’s accounts on Friday the 28th by rpdillon on Monday August 17, 2020 @07:28PM (#24193509)
This behavior is now the norm in my experience, including browser extensions, mobile apps, and websites. I experience breakage through no action of my own, triggered remotely by the developer. While I agree that it's very much like malware, I'm simply pointing out that this is the rule, rather than the exception, with commercial software today.
Re:Apple to kill Epic’s accounts on Friday the 28th by _qulr on Monday August 17, 2020 @06:21PM (#24192931)
Mac malware, come on. There's no Developer ID or notarization on iOS, it's App Store only.