summaryrefslogtreecommitdiff
path: root/4c/eff276fffc11bba67e6f990b3cc6d86d4af185
blob: d8891766d94db3c371576743f69508ab79f54c8f (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
	helo=mx.sourceforge.net)
	by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <stick@gk2.sk>) id 1XgreO-0007LI-Uv
	for bitcoin-development@lists.sourceforge.net;
	Wed, 22 Oct 2014 08:52:13 +0000
X-ACL-Warn: 
Received: from mail-wg0-f49.google.com ([74.125.82.49])
	by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1XgreM-00059o-Vw
	for bitcoin-development@lists.sourceforge.net;
	Wed, 22 Oct 2014 08:52:12 +0000
Received: by mail-wg0-f49.google.com with SMTP id x12so3282171wgg.32
	for <bitcoin-development@lists.sourceforge.net>;
	Wed, 22 Oct 2014 01:52:04 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20130820;
	h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to
	:cc:subject:references:in-reply-to:content-type
	:content-transfer-encoding;
	bh=CIW18dnLdeS93LcAKzT2bFRa9Lu8dziPDvpbUAMARo0=;
	b=T8VNX1/WSIoXz7K7Rz1+MbqIQaMX5+mtLNRIlufxHDz7Jc3eNDwE/8pShIjUH+DSgn
	a3MkAOmmAXHe54bYoSiFoTRW0wbQZC6gFscAuFdl5XAsAzo0hj7utYwhBWunsmP0dQed
	8NZUIlBbHUaPEKnFD4ER3jyAzZE+UGvsY8c8NaQ3oK+9s0j/3/dW4PkytRj1HtgmPUpi
	Vr1RmxGUOZvadbGnceCrqos2IPYtVn4H1VZbjTh8UusxheZin7oApeWZTCK762uu7GRu
	ArtfBQyJlZdBN3NxeYT7IqfyfoxoYolWAj5BiqzUu7j+M/z+wCaNEo57Q1A5/zbMedsF
	D/Cw==
X-Gm-Message-State: ALoCoQlpPcXoDcAopW1qz3Pe12ZKSKG/JE3vDhZ5JMBl1drTWHILahvQnQVsLy/8zh+9zPLukKul
X-Received: by 10.180.95.41 with SMTP id dh9mr1335253wib.0.1413967924558;
	Wed, 22 Oct 2014 01:52:04 -0700 (PDT)
Received: from tetra.site ([185.68.216.104])
	by mx.google.com with ESMTPSA id da10sm628814wib.0.2014.10.22.01.52.02
	for <multiple recipients>
	(version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
	Wed, 22 Oct 2014 01:52:03 -0700 (PDT)
Message-ID: <54477031.8040200@gk2.sk>
Date: Wed, 22 Oct 2014 10:52:01 +0200
From: Pavol Rusnak <stick@gk2.sk>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
	rv:31.0) Gecko/20100101 Thunderbird/31.1.0
MIME-Version: 1.0
To: Chris D'Costa <chrisjdcosta@gmail.com>
References: <CAKzHBKkHpod+7T0uCtESVNFmgFAbGF8-AFJxKmfUwA-pkt_BrA@mail.gmail.com>	<5446C872.7050302@gk2.sk>
	<CAC0TF=mi5WUHf5wvU0YDOSuUiyrEUH_+QVNGTBr_RYQEzY7QYw@mail.gmail.com>
In-Reply-To: <CAC0TF=mi5WUHf5wvU0YDOSuUiyrEUH_+QVNGTBr_RYQEzY7QYw@mail.gmail.com>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-Spam-Score: 1.5 (+)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	1.5 RCVD_IN_PSBL           RBL: Received via a relay in PSBL
	[185.68.216.104 listed in psbl.surriel.com]
X-Headers-End: 1XgreM-00059o-Vw
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] cryptographic review requested
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Wed, 22 Oct 2014 08:52:13 -0000

On 10/22/2014 10:46 AM, Chris D'Costa wrote:
> Looks great, but how would you resolve the problem of knowing for certain
> that the public key you have received to encrypt the message is not from a
> MITM?

Isn't this the same problem with PGP?

-- 
Best Regards / S pozdravom,

Pavol Rusnak <stick@gk2.sk>