<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Jan 1, 2015 at 2:09 AM, Ralf Senderek <span dir="ltr"><<a href="mailto:crypto@senderek.ie" target="_blank">crypto@senderek.ie</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">The Crypto Pi<br>
<br></blockquote><div><br></div><div>There does not appear to be anything Pi-specific about this. Am I missing something?</div><div><br></div><div>/ji</div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
This year has had some devastating news about the state of the internet infrastructure in store and came with some<br>
disillusion about the vulnerability of tools we use day by day. And BTW it had turned out, that Johnny still can't encrypt.<br>
<br>
To change that, I've put some effort into developing the crypto pi.<br>
<br>
While running on a minimalist Linux OS with only the necessary<br>
tools installed, the crypto pi is different both from internet servers and insecure endpoints, and helps Johnny to establish secure<br>
communication that is always encrypted, without burdening him with<br>
complex tasks that would only make him avoid using secure communication.<br>
<br>
The crypto pi is in its early stages of its infant life and although<br>
it's working and looking great, it has not got the most important<br>
ingredient for a happy life (yet), peer-review.<br>
<br>
So I'd like to ask all of you, who think a well-designed, isolated<br>
crypto box under the sole control of its user, capable of doing message<br>
encryption reliably, may improve the situation we're facing today,<br>
to give a hand and scrutinize the design and implementation of the<br>
crypto pi. Let's make the crypto pi a success in 2015, together.<br>
<br>
The concept of secure communication using the crypto pi relies on<br>
several assumptions, not everyone will agree to:<br>
<br>
1) Johnny will be able to communicate securely with people he knows,<br>
if he had been able to exchange an initial secret information<br>
(on a piece of paper, via telephone, or some other way)<br>
<br>
2) Johnny's endpoint device is not trustworthy, as it runs all kinds<br>
of complex programs that are prone to attack the secrets on<br>
his device without notice in unforeseeable ways.<br>
<br>
3) Apart from feeding the crypto pi with the initial secret and an email<br>
address of the recipient (by filling out a form) Johnny has nothing<br>
to do with key management, but will be able to verify that message<br>
encryption has been performed.<br>
<br>
4) All secrets are stored on the crypto pi and messages leave the<br>
crypto pi AES-encrypted with a strong randomly generated key.<br>
The crypto pi does not use public key cryptography, there is no PKI<br>
nor CAs involved.<br>
<br>
5) Johnny uses one single secret that he alone knows to establish an<br>
encrypted tunnel to the crypto pi over which he interacts with the<br>
web server on the crypto pi to read and write messages.<br>
<br>
6) The local network in which the crypto pi works is not trustworthy,<br>
so all information that originates from the crypto pi is encrypted<br>
and only encrypted information that enters the crypto pi will be<br>
processed inside.<br>
<br>
7) Although desirable, ensuring anonymity is not a pre-requisite of<br>
the crypto pi's design (at the moment).<br>
<br>
8) All source code is licensed under GPL.<br>
<br>
Fortunately, the crypto pi has a home (<a href="http://crypto-pi.com" target="_blank">crypto-pi.com</a>) where you can get<br>
more detailed information about its fundamental concepts and implementation. Make sure, your criticism and constructive suggestions will be used to<br>
improve this project.<br>
<br>
Best wishes for 2015<br>
<br>
Ralf Senderek<br>
<br>
<br>
______________________________<u></u>_________________<br>
The cryptography mailing list<br>
<a href="mailto:cryptography@metzdowd.com" target="_blank">cryptography@metzdowd.com</a><br>
<a href="http://www.metzdowd.com/mailman/listinfo/cryptography" target="_blank">http://www.metzdowd.com/<u></u>mailman/listinfo/cryptography</a><br>
</blockquote></div><br></div></div>