Delivery-Date: Tue, 03 Feb 2015 14:33:36 -0500
Return-Path: <tor-talk-bounces@lists.torproject.org>
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on moria.seul.org
X-Spam-Level: 
X-Spam-Status: No, score=-4.8 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_MED,
	RP_MATCHES_RCVD,URIBL_BLOCKED autolearn=ham version=3.3.1
X-Original-To: archiver@seul.org
Delivered-To: archiver@seul.org
Received: from eugeni.torproject.org (eugeni.torproject.org [38.229.72.13])
	(using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by khazad-dum.seul.org (Postfix) with ESMTPS id 1FD141E0AE2
	for <archiver@seul.org>; Tue,  3 Feb 2015 14:33:35 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id BA0AB33679;
	Tue,  3 Feb 2015 19:33:31 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 01C1F33574
 for <tor-talk@lists.torproject.org>; Tue,  3 Feb 2015 19:33:29 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at 
Received: from eugeni.torproject.org ([127.0.0.1])
 by localhost (eugeni.torproject.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id 6haHjch1b05x for <tor-talk@lists.torproject.org>;
 Tue,  3 Feb 2015 19:33:28 +0000 (UTC)
Received: from ip-172-31-0-247.us-west-2.compute.internal
 (ec2-54-213-166-118.us-west-2.compute.amazonaws.com [54.213.166.118])
 by eugeni.torproject.org (Postfix) with ESMTP id D212B3352C
 for <tor-talk@lists.torproject.org>; Tue,  3 Feb 2015 19:33:28 +0000 (UTC)
Received: from [192.168.1.145] (rrcs-24-43-0-6.west.biz.rr.com [24.43.0.6])
 (Authenticated sender: mike)
 by ip-172-31-0-247.us-west-2.compute.internal (Postfix) with ESMTPSA id
 E753EA044F
 for <tor-talk@lists.torproject.org>; Tue,  3 Feb 2015 19:33:19 +0000 (UTC)
Message-ID: <54D12284.4020705@confidantmail.org>
Date: Tue, 03 Feb 2015 11:33:24 -0800
From: Mike Ingle <mike@confidantmail.org>
User-Agent: Thunderbird 2.0.0.22 (Windows/20090605)
MIME-Version: 1.0
To: tor-talk@lists.torproject.org
Subject: Re: [tor-talk] Confidant Mail
X-BeenThere: tor-talk@lists.torproject.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: tor-talk@lists.torproject.org
List-Id: "all discussion about theory, design,
 and development of Onion Routing" <tor-talk.lists.torproject.org>
List-Unsubscribe: <https://lists.torproject.org/cgi-bin/mailman/options/tor-talk>, 
 <mailto:tor-talk-request@lists.torproject.org?subject=unsubscribe>
List-Archive: <http://lists.torproject.org/pipermail/tor-talk/>
List-Post: <mailto:tor-talk@lists.torproject.org>
List-Help: <mailto:tor-talk-request@lists.torproject.org?subject=help>
List-Subscribe: <https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk>, 
 <mailto:tor-talk-request@lists.torproject.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Errors-To: tor-talk-bounces@lists.torproject.org
Sender: "tor-talk" <tor-talk-bounces@lists.torproject.org>

On 2/3/2015 10:31 AM, Kevin wrote:
> On 2/3/2015 12:33 PM, krishna e bera wrote:
>> On 15-02-02 09:57 PM, Mike Ingle wrote:
>>> http://www.confidantmail.org
>>> Mike Ingle <mike@confidantmail.org>
>>> d2b89e6f95e72e26e0c917d02d1847dfecfcd0c2
>> I am curious why someone delivering security and privacy software does
>> not have HTTPS on their webserver.  Also what is that string after your
>> email address for?
>>
> That string looks like a key
>
That string is indeed a key. The format is Name <email> keyid
and you can search for either the name or the keyid to find someone's 
key. If you search for the keyid
you know you have the right key. If you search for the name, you have to 
verify the keyid somehow.

I don't have HTTPS because there is nothing secret on the site, and 
because I don't place much trust in it.
The keyid in the announce posting has signed the code signing key, and 
the code signing key has signed
all the binaries, so you can validate the code integrity.

On 2/3/2015 9:26 AM, Steve Weis wrote:
> Why are the Confident Mail PGP key, binaries, and signatures are all 
> served over http?
>
> Skimming over the code, it lacks any documentation or tests. I see 
> blocks of commented-out code scattered through the files. I also see a 
> lot of potentially unsafe input being concatenated together and used 
> throughout the code.
>
> I recommend that you warn people not to use this software for anything 
> real yet. It needs a lot of work.
The commented-out code is mostly debug output and some test drivers. 
There was another separate test driver
which is not part of the release. I left that in for now in case I need 
to test something; it will be removed eventually.
The code has been tested quite a bit on Windows and Linux, including Tor 
and I2P.

The program is written in Python, which is an interpreted language with 
counted strings, so concatenating
strings is not a dangerous operation. There are functions to validate 
the blocks using regular expressions.
There is also an option to open untrusted messages text-only.

The security is done using GPG, not in the Python code. The client also 
does not accept incoming connections.
It's already being used to exchange large files and works fine. Yes it 
is beta software, but it is already more
secure than most conventional email.

MacOS binary package is close to working.

Mike Ingle <mike@confidantmail.org> 
d2b89e6f95e72e26e0c917d02d1847dfecfcd0c2


-- 
tor-talk mailing list - tor-talk@lists.torproject.org
To unsubscribe or change other settings go to
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk

