5 ms·

You missed the main holy grail requirement: open source. Nothing closed source can be trusted.

bellerocky 12y ago
Complete transparency from end to end would require more than just open source. You'd have to be able to build and run the software itself, which on an iPhone costs $99 a year to do and poses significant technical challenges. To go further you'd have to transparency at the hardware level as well. Your own device, built by you, with software you compiled yourself. Maybe then you'd achieve the level of security that you're aiming for, assuming you are competent enough to evaluate the software and hardware you are using.
- rdtsc 12y ago
  It wouldn't be for iPhone. For Android it might work but you'd need a hardware platform you trust (one where you are sure no radio baseband processor is going to snoop at your memory any time it wants), use AOSP and then an open source app. Then also if there are any registration or routing services those would have to be open source as well.
nobbyclark 12y ago
How do you know that the app published on the App Store is the same one you have the source code for? Can't I can just give you some source code then release something else entirely?
- lifeisstillgood 12y ago
  I could compile the source for iPhone (well someone could I have no idea. Probably some SDK). Then compare hashes.
  - khc 12y ago
    Actually you cannot. Rebuilding from the same source almost never yield identical binaries.
    - gioi 12y ago
      Actually you could. They are called "deterministic builds". But this would require some kind of effort from project maintainers.
      - Cederfjard 12y ago
        I'm quite unknowledgeable about this, but from what little I understand: That is actually a very major effort in many cases, isn't it?
      - gtufano 12y ago
        You cannot do that for iOS binaries, because they are signed by Apple before publishing on the Store (and so the hash will change).
        onedognight 12y ago
        You can avoid the signature when hashing.
- gcb4 12y ago
  compile yourself. or download from a source you trust and compare hash from another trustworthy source. just like anything you download. unless you run gentoo, but then how do you trust your sources, etc and if you have a closed source phone os that only allows to install from their store... well you have to learn to crawl before you walk.
- imaginenore 12y ago
  The way it's usually done is you publish your A) exact compilation settings B) hash checksums for everything, including the resulting binaries You probably can't do this on iOS, but on Android you can have a third party app monitoring the changes, or simply disabling the automatic updates altogether.

Complete transparency from end to end would require more than just open source. You'd have to be able to build and run the software itself, which on an iPhone costs $99 a year to do and poses significant technical challenges. To go further you'd have to transparency at the hardware level as well. Your own device, built by you, with software you compiled yourself. Maybe then you'd achieve the level of security that you're aiming for, assuming you are competent enough to evaluate the software and hardware you are using.

rdtsc 12y ago
It wouldn't be for iPhone. For Android it might work but you'd need a hardware platform you trust (one where you are sure no radio baseband processor is going to snoop at your memory any time it wants), use AOSP and then an open source app. Then also if there are any registration or routing services those would have to be open source as well.

nobbyclark 12y ago

How do you know that the app published on the App Store is the same one you have the source code for? Can't I can just give you some source code then release something else entirely?

lifeisstillgood 12y ago
I could compile the source for iPhone (well someone could I have no idea. Probably some SDK). Then compare hashes.
- khc 12y ago
  Actually you cannot. Rebuilding from the same source almost never yield identical binaries.
  - gioi 12y ago
    Actually you could. They are called "deterministic builds". But this would require some kind of effort from project maintainers.
    - Cederfjard 12y ago
      I'm quite unknowledgeable about this, but from what little I understand: That is actually a very major effort in many cases, isn't it?
    - gtufano 12y ago
      You cannot do that for iOS binaries, because they are signed by Apple before publishing on the Store (and so the hash will change).
      - onedognight 12y ago
        You can avoid the signature when hashing.
gcb4 12y ago
compile yourself. or download from a source you trust and compare hash from another trustworthy source. just like anything you download. unless you run gentoo, but then how do you trust your sources, etc and if you have a closed source phone os that only allows to install from their store... well you have to learn to crawl before you walk.
imaginenore 12y ago
The way it's usually done is you publish your A) exact compilation settings B) hash checksums for everything, including the resulting binaries You probably can't do this on iOS, but on Android you can have a third party app monitoring the changes, or simply disabling the automatic updates altogether.