4 ms·

There goes Moxies justification for using only the Playstore for Signal... And I'm waiting for the first supply-chain attack resulting from Google signing a ro

by corty 5y ago

There goes Moxies justification for using only the Playstore for Signal... And I'm waiting for the first supply-chain attack resulting from Google signing a rootkit, Microsoft-style...

izacus 5y ago
> There goes Moxies justification for using only the Playstore for Signal... Moxie is fine with this state of affairs on iOS - I'm not sure why this would change anything on that front?
- corty 5y ago
  Moxie complained about F-Droid recompiling and resigning his stuff. And cited this as his reason to use only the Playstore. But I guess things were more about analytics and control after all.
  - m-p-3 5y ago
    Moxie can use F-Droid with his own signature if he supplies a reproducible build. https://f-droid.org/en/docs/Reproducible_Builds/ https://f-droid.org/en/docs/Reproducible_Builds/
    - Aissen 5y ago
      Which in theory Signal supports; anyone tried it lately ? https://github.com/signalapp/Signal-Android/tree/master/reproducible-builds https://github.com/signalapp/Signal-Android/tree/master/repr...
  - tssva 5y ago
    You are trying to place events which happened in the past under a completely different set of circumstances into the circumstances of today and then are drawing a conclusion from that.
    - corty 5y ago
      Yes. It is a nice natural experiment as to Moxies motivations and principles, because only a very select set of circumstances has changed: Software authors can no longer control their signatures on Android. That time has passed is not relevant, or at best relevant to explain some change of heart over time.
tapoxi 5y ago
AAB supports a code transparency feature: https://developer.android.com/guide/app-bundle/code-transparency https://developer.android.com/guide/app-bundle/code-transpar...
- toast0 5y ago
  > The code transparency file does not verify resources, assets, the Android Manifest, or any other files that are not DEX files or native libraries contained in the lib/ folder. > Important: The Android OS does not verify code transparency files at install time, and continues to rely on the APK signing schemes for verification of any installed APKs. This is like having checksums in a Readme. If nobody checks them (and that's the likely case, since the OS doesn't), it doesn't matter if they differ from the distributed files. It's still the case that Google is taking over the code signing roles, so that the user's OS will no longer tell the difference between a developer signed update and a Google signed update. This is a negative for security and transparency, regardless of the size benefits and regardless of the fact that the Apple App Store has operated in this fashion since the beginning.

by corty 5y ago

There goes Moxies justification for using only the Playstore for Signal... And I'm waiting for the first supply-chain attack resulting from Google signing a rootkit, Microsoft-style...

izacus 5y ago

> There goes Moxies justification for using only the Playstore for Signal... Moxie is fine with this state of affairs on iOS - I'm not sure why this would change anything on that front?

corty 5y ago
Moxie complained about F-Droid recompiling and resigning his stuff. And cited this as his reason to use only the Playstore. But I guess things were more about analytics and control after all.
- m-p-3 5y ago
  Moxie can use F-Droid with his own signature if he supplies a reproducible build. https://f-droid.org/en/docs/Reproducible_Builds/ https://f-droid.org/en/docs/Reproducible_Builds/
  - Aissen 5y ago
    Which in theory Signal supports; anyone tried it lately ? https://github.com/signalapp/Signal-Android/tree/master/reproducible-builds https://github.com/signalapp/Signal-Android/tree/master/repr...
- tssva 5y ago
  You are trying to place events which happened in the past under a completely different set of circumstances into the circumstances of today and then are drawing a conclusion from that.
  - corty 5y ago
    Yes. It is a nice natural experiment as to Moxies motivations and principles, because only a very select set of circumstances has changed: Software authors can no longer control their signatures on Android. That time has passed is not relevant, or at best relevant to explain some change of heart over time.

tapoxi 5y ago

AAB supports a code transparency feature: https://developer.android.com/guide/app-bundle/code-transparency https://developer.android.com/guide/app-bundle/code-transpar...

toast0 5y ago
> The code transparency file does not verify resources, assets, the Android Manifest, or any other files that are not DEX files or native libraries contained in the lib/ folder. > Important: The Android OS does not verify code transparency files at install time, and continues to rely on the APK signing schemes for verification of any installed APKs. This is like having checksums in a Readme. If nobody checks them (and that's the likely case, since the OS doesn't), it doesn't matter if they differ from the distributed files. It's still the case that Google is taking over the code signing roles, so that the user's OS will no longer tell the difference between a developer signed update and a Google signed update. This is a negative for security and transparency, regardless of the size benefits and regardless of the fact that the Apple App Store has operated in this fashion since the beginning.