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
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <mh.in.england@gmail.com>) id 1Wgw7o-0007hD-7h
for bitcoin-development@lists.sourceforge.net;
Sun, 04 May 2014 13:06:36 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.219.45 as permitted sender)
client-ip=209.85.219.45; envelope-from=mh.in.england@gmail.com;
helo=mail-oa0-f45.google.com;
Received: from mail-oa0-f45.google.com ([209.85.219.45])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Wgw7n-0004jF-92
for bitcoin-development@lists.sourceforge.net;
Sun, 04 May 2014 13:06:36 +0000
Received: by mail-oa0-f45.google.com with SMTP id eb12so7320231oac.18
for <bitcoin-development@lists.sourceforge.net>;
Sun, 04 May 2014 06:06:29 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.60.146.201 with SMTP id te9mr27261901oeb.38.1399208789657;
Sun, 04 May 2014 06:06:29 -0700 (PDT)
Sender: mh.in.england@gmail.com
Received: by 10.76.96.180 with HTTP; Sun, 4 May 2014 06:06:29 -0700 (PDT)
In-Reply-To: <20140502204146.GD62950@giles.gnomon.org.uk>
References: <CANEZrP15TKPcWnjdnfbRd9KxrS_5F=07gTL1DxyMo1os-sVOpA@mail.gmail.com>
<20140502204146.GD62950@giles.gnomon.org.uk>
Date: Sun, 4 May 2014 15:06:29 +0200
X-Google-Sender-Auth: GF8xXsMKZyLTPmFUEiXOBF7nn-s
Message-ID: <CANEZrP34xJrFnntQqX5o88MyB=+W339kcwvZPojWt2hPF3HJwA@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Roy Badami <roy@gnomon.org.uk>
Content-Type: multipart/alternative; boundary=047d7b5d524edfce3204f892ae73
X-Spam-Score: -0.5 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(mh.in.england[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1Wgw7n-0004jF-92
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] BIP70 implementation guidance
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: Sun, 04 May 2014 13:06:36 -0000
--047d7b5d524edfce3204f892ae73
Content-Type: text/plain; charset=UTF-8
>
> e.g. in the UK sole traders (that is, unincorporated businesses) can't
> get EV certs because the UK doesn't maintain a trade register of such
> businesses
>
Sole traders can just trade under their own name, or their email address,
or their domain name, heck even their telephone number if someone sets up
an SMS verifying CA. I don't worry too much about such things - the point
of the cert is just to disambiguate the payment so people can't get
confused into paying the wrong entity.
Companies that can't get EV certs cause us pain indirectly by making users
less certain about what they're expecting to see when they pay a company,
making confusion attacks a bit easier, but I bet it'll be a minor issue in
practice.
--047d7b5d524edfce3204f892ae73
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #c=
cc solid;padding-left:1ex"><div class=3D"">e.g. in the UK sole traders (tha=
t is, unincorporated businesses) can't<br>
</div>
get EV certs because the UK doesn't maintain a trade register of such<b=
r>
businesses<br></blockquote><div><br></div><div>Sole traders can just trade =
under their own name, or their email address, or their domain name, heck ev=
en their telephone number if someone sets up an SMS verifying CA. I don'=
;t worry too much about such things - the point of the cert is just to disa=
mbiguate the payment so people can't get confused into paying the wrong=
entity.</div>
<div><br></div><div>Companies that can't get EV certs cause us pain ind=
irectly by making users less certain about what they're expecting to se=
e when they pay a company, making confusion attacks a bit easier, but I bet=
it'll be a minor issue in practice.</div>
<div><br></div></div></div></div>
--047d7b5d524edfce3204f892ae73--
|
