←back to thread

Apple vs the Law

(formularsumo.co.uk)
377 points tempodox | 1 comments | | HN request time: 0.215s | source
Show context
grishka ◴[] No.44529279[source]
> "...unfortunately, it's impossible to do all the complex engineering to comply with the Commission's current interpretation of the DMA..."

There's nothing complex and impossible about removing some "if" statements responsible for code signature enforcement.

replies(9): >>44529310 #>>44529322 #>>44529363 #>>44529431 #>>44529446 #>>44529695 #>>44530078 #>>44531016 #>>44531269 #
mattlondon ◴[] No.44530078[source]
I suspect it goes a lot deeper than just a single if-statement somewhere, and hundreds of thousands of lines of code and various interfaces and all the rest are built on the core assumption of the signatures being there and the packages etc being signed.

These sort of things can be tricky to refactor and more complex than they first seem. For example I recently spent the past 12 weeks or so just moving some fields around on a CRUD app (not adding or removing - just changing their order!) because there were assumptions built on assumptions built on assumptions about what order things are in and what comes first and what has already been done or not and so on. What ostensibly seemed trivial, actually required almost a complete rewrite of whole parts of the CRUD app to overcome the assumptions and implied behavior of what happens when and how.

replies(1): >>44530868 #
1. grishka ◴[] No.44530868[source]
They share a lot of "AMFI" infrastructure between iOS and macOS, with macOS having a much more permissive security model (you can run self-signed code) while still retaining "private" entitlements for sensitive private APIs, only available to Apple-signed apps. Unless you disable SIP, then you can just do whatever.

(Disclaimer: I may be wrong, I haven't done much of my own research, it's just things I read in various articles over the years)