With all the respect what they have done so far, I can't see any reason why this is securer than the other mobile phones..
With the latest NSA stuff, I came to conclusion that a true secure system can only be built under these conditions and just to put it out there, this is just my opinion;
- A computer company that manufactures their own hardware such as hard drive, ram, cables, network cards.
- An OS that is newly written and not based on any other existing operating systems.
- Building the whole system with INDEPENDENT hardware and software mentioned above.
- Keeping the mobile device's source code offline from Internet as much as possible
These are just the first steps on developing a secure system, then comes the mobile network architecture and encryption etc.
I admit, it is not an easy job but, trying to develop a secure system with "not secure" development tools is not the right way to go :)
You're probably right about what's involved in building a truly secure smartphone from scratch that we can trust.
It's an interesting thought experiment, but I wonder if we can satisfy many use cases without having to build a truly secure smartphone.
For example, if I just want to have voice calls to a handful of people with the content of the calls encrypted, then perhaps I can just plug in a "scrambler box" between my untrusted off-the-shelf phone and my audio headset?
So rather than designing a secure phone where we trust the wifi stack, the baseband stack, the bluetooth stack, the graphics stack, the USB stack, the flash storage stack because we've designed them from scratch, all we have to design is a little scrambler box that just has audio in, audio out, some mechanism for key generation and exchange, and only needs a laughably modest CPU to do the encryption.
Don't really need an OS at all - single process and static memory allocation should suffice.
The audio encoding/decoding and encryption/decryption don't sound too hard to implement from scratch. It's the interoperability with the rest of the world and the UI that makes implementing a whole smartphone so hard.
[I do wonder though how well our scrambled audio will make it through the phone network which is applying lots of clever compression designed for speech.]
If we assume we can mostly trust hardware designs that are at least 30 years old then we can probably avoid designing all the hardware from scratch - e.g. there's probably some sort of Z80 clone CPU we can copy.
The mechanism for key generation and management sounds a bit tricky though. The user would need some way to add his contacts' keys to his scrambler box.
A keyboard and LCD display to type keys in by hand would be secure but impractical for long keys.
The level of tech needed to read a key file from a FAT filing system on a USB stick might be too high to be easily implemented securely. Any ideas?
I'm aware of the famous "trusting trust" paper, but I'm not sure we need to worry too much about the compiler used to build the software running on our scrambler box. All we need to do is choose a compiler released before we started out project and never upgrade it. It is hard to imagine a compiler backdoor that would automatically recognize that the intent of our code is to encrypt data and undetectably comprise it (though it would be wise I guess to avoid any existing implementations of cryptographic primitives).
It is an exciting idea but the two obstacles I can see are:
1) When asked, people may say they want security and privacy - but in practice convenience and functionality win.
2) Among people who genuinely need secure communications, encrypting the content of calls/texts is good, but isn't normally sufficient - they're still vulnerable to traffic analysis.
By traffic analysis I mean that even though the adversary can't read the content, they can still figure out things like:
"Mr X is the ring-leader of the freedom fighters since his phone is used to send encrypted messages to several other phones, which then send messages on to several other phones."
"Mr Y is guilty of orchestrating the protests since we saw a strong correlation between the times of the protests and messages coming from his phone."
So I'm not sure how popular the product would actually be. Unless we can somehow solve the traffic analysis problem.
Traffic analysis is not a problem if we could ever gotten that far.
We can solve it by faking the signals and sending it every x timestamp. So they will think there is a traffic but there is not. This is the first came to my mind but i don't think it is a big issue at all.
Marketing of this, is a little bit different. Of course, you will not sell if you say you have the most secure phone. But if you polish it with some exciting features which does not exist yet? :)
With the latest NSA stuff, I came to conclusion that a true secure system can only be built under these conditions and just to put it out there, this is just my opinion;
- A computer company that manufactures their own hardware such as hard drive, ram, cables, network cards.
- An OS that is newly written and not based on any other existing operating systems.
- Building the whole system with INDEPENDENT hardware and software mentioned above.
- Keeping the mobile device's source code offline from Internet as much as possible
These are just the first steps on developing a secure system, then comes the mobile network architecture and encryption etc.
I admit, it is not an easy job but, trying to develop a secure system with "not secure" development tools is not the right way to go :)