4 ms·

The only scenario that comes to mind would be Google repackaging a build after some subtle changes, signing it and sending to a lawful intercept target. Are th

The only scenario that comes to mind would be Google repackaging a build after some subtle changes, signing it and sending to a lawful intercept target. Are there other cases where the developer does not sign the package aside from selling the package to Google?

can16358p 3y ago
Apple does something similar to create optimized versions of the app for different devices/OS versions (presumably).
- LinuxBender 3y ago
  Interesting. Do Apple then submit their optimized diffs to the developer and have them uptake the changes so the source is optimized? Or would the developer have to de-compile the artifacts and reverse engineer the optimizations to see what was changed, added or removed? It seems like this would make attestation and audits challenging for apps used by b2b financial customers.
  - nerdjon 3y ago
    I would imagine that this is similar to the same shared security model that you would use within AWS and other Cloud Providers. At some point you have to point to their documentation and how they do things as being out of your control but possibly audited on its own. But if you are really worried for iOS it is optional. I don't see any capabilities regarding your first question outside of testing specific devices through TestFlight, but I would think it is fairly safe to assume that Apple has put a lot of work into making sure this works consistently between devices. It is also entirely possible that, like working with Cloud Providers, that there is a difference between what normal users can do and what can be done with NDA's and other contracts signed.
- tempay 3y ago
  For some details: https://help.apple.com/xcode/mac/current/#/devbbdc5ce4f https://help.apple.com/xcode/mac/current/#/devbbdc5ce4f
SAI_Peregrinus 3y ago
Google takes the bundle, and builds a bunch of binaries for different architectures & device OS versions. The changes aren't subtle, they delete things the user's device doesn't need and sign the result. E.g. if the user has a 32-bit ARM device they'll delete 64-bit ARM code from the bundle when building the binary, and likewise for the reverse. That saves users both mobile data and storage space.

can16358p 3y ago

Apple does something similar to create optimized versions of the app for different devices/OS versions (presumably).

LinuxBender 3y ago
Interesting. Do Apple then submit their optimized diffs to the developer and have them uptake the changes so the source is optimized? Or would the developer have to de-compile the artifacts and reverse engineer the optimizations to see what was changed, added or removed? It seems like this would make attestation and audits challenging for apps used by b2b financial customers.
- nerdjon 3y ago
  I would imagine that this is similar to the same shared security model that you would use within AWS and other Cloud Providers. At some point you have to point to their documentation and how they do things as being out of your control but possibly audited on its own. But if you are really worried for iOS it is optional. I don't see any capabilities regarding your first question outside of testing specific devices through TestFlight, but I would think it is fairly safe to assume that Apple has put a lot of work into making sure this works consistently between devices. It is also entirely possible that, like working with Cloud Providers, that there is a difference between what normal users can do and what can be done with NDA's and other contracts signed.
tempay 3y ago
For some details: https://help.apple.com/xcode/mac/current/#/devbbdc5ce4f https://help.apple.com/xcode/mac/current/#/devbbdc5ce4f

SAI_Peregrinus 3y ago

Google takes the bundle, and builds a bunch of binaries for different architectures & device OS versions. The changes aren't subtle, they delete things the user's device doesn't need and sign the result. E.g. if the user has a 32-bit ARM device they'll delete 64-bit ARM code from the bundle when building the binary, and likewise for the reverse. That saves users both mobile data and storage space.