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
107
108
109
110
111
112
113
114
115
116
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <rick.wesson@iidf.org>) id 1Td8l3-0002hW-KS
for bitcoin-development@lists.sourceforge.net;
Tue, 27 Nov 2012 00:10:37 +0000
X-ACL-Warn:
Received: from mail-yh0-f47.google.com ([209.85.213.47])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Td8l2-0001aF-Sp
for bitcoin-development@lists.sourceforge.net;
Tue, 27 Nov 2012 00:10:37 +0000
Received: by mail-yh0-f47.google.com with SMTP id g23so1498007yhg.34
for <bitcoin-development@lists.sourceforge.net>;
Mon, 26 Nov 2012 16:10:31 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=google.com; s=20120113;
h=mime-version:in-reply-to:references:date:message-id:subject:from:to
:cc:content-type:x-gm-message-state;
bh=pcIX/htUYZ+Ti+lswUYyw1iwZoRpweFzG8nOpEpthQk=;
b=fy5p8hIpeO/T0FP6azcrFW41CcHnCg049kD9yAw0f5SHIyj7lfvTBIFQBHJhPrha5W
nMP/AezVO8sCOY0Nrz/sCp+oZ+5UAVPXZA4tkNo6YlOn+meypWO4/GkD2jQAiHd2aIS6
EmPhV8uRNF8NQWN6AiiF7jEt4U8nmaHw/4XNC58ehoUNVQltwY6pOFRXBkLvcQKZ3KeH
MPrkNOS00Fwf2yUzUeauBLJjG5dL73R4/+F8EvmipENnVk9VqAPPWqEet0zUU0VM99Id
+ss1zzVwuA4hyvLBzml/qGYHHR90p+nO1fu2UeO7BMwy7JOCWS+De2do0Xo0GsA4Caeh
ERQw==
MIME-Version: 1.0
Received: by 10.101.180.27 with SMTP id h27mr3819750anp.60.1353974562645; Mon,
26 Nov 2012 16:02:42 -0800 (PST)
Received: by 10.101.69.3 with HTTP; Mon, 26 Nov 2012 16:02:42 -0800 (PST)
In-Reply-To: <CA+8xBpe6x_aB_-Q5VLh164eoqqqwWBa1sy=UE-0u=jAD2+xTXg@mail.gmail.com>
References: <CABsx9T0PsGLEAWRCjEDDFWQrb+DnJWQZ7mFLaZewAEX6vD1eHw@mail.gmail.com>
<CA+8xBpe6x_aB_-Q5VLh164eoqqqwWBa1sy=UE-0u=jAD2+xTXg@mail.gmail.com>
Date: Mon, 26 Nov 2012 16:02:42 -0800
Message-ID: <CAJ1JLttwSdjYUm2zFAQ4XczEaoG29u-Nq8gjhsn-rjG1yWzFVQ@mail.gmail.com>
From: Rick Wesson <rick@support-intelligence.com>
To: Jeff Garzik <jgarzik@exmulti.com>
Content-Type: text/plain; charset=ISO-8859-1
X-Gm-Message-State: ALoCoQnbtrPAhonCOfDsgUMnhqSL+S6LAyGuUxzjufbdAtsfR0Kiq8tF+9NQOKSt5A/p8H6bAq2w
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
X-Headers-End: 1Td8l2-0001aF-Sp
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Payment Protocol Proposal:
Invoices/Payments/Receipts
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: Tue, 27 Nov 2012 00:10:37 -0000
I hope you all take a moment to see what DANE leverages with DNSSEC
and SelfSigned x.509 certs. DANE provides the capability for any
entity to associate a self signed certificate with a domain name. This
capability removes the critical path of whitelists and/or Root CA
certs.
Another nifty thing is that it can associate a cert to a domain and a
payment address, if one were to put said address in the DNS :)
Now I am sure the majority of the bitcoin user-base desires anonymity,
but as a merchant I would like to be knowable and wouldn't mind it if
my identity and those of my transactions were "known" and associated
both with my domains and x.509 cert. In most commercial transactions
(which include many of those that leverage invoices) identity is
important, at least for the merchant.
-rick
On Mon, Nov 26, 2012 at 3:52 PM, Jeff Garzik <jgarzik@exmulti.com> wrote:
> On Mon, Nov 26, 2012 at 5:37 PM, Gavin Andresen <gavinandresen@gmail.com> wrote:
>> This is the next big "lets all agree to do things the same way" thing
>> I think we should tackle. I'm particularly looking for feedback from
>> other bitcoin client developers, even if it is just a quick "looks
>> reasonable, if everybody else is going to do it then I will
>> (eventually) too..."
>
> Comments:
>
> 1) Payment message should include ability to specify the transaction
> _or_ a transaction id sent via normal means over the network.
>
> 2) I think a significant bitcoin userbase will want to operate outside
> the full root-CA chain. Just look at https:// websites now.
> Self-signed certs are quite common, because it is easier, while being
> more secure than http://
>
> So some provision for self-signed certs, a use case in wide use
> elsewhere, or equivalent thereof, seems reasonable.
>
> --
> Jeff Garzik
> exMULTI, Inc.
> jgarzik@exmulti.com
>
> ------------------------------------------------------------------------------
> Monitor your physical, virtual and cloud infrastructure from a single
> web console. Get in-depth insight into apps, servers, databases, vmware,
> SAP, cloud infrastructure, etc. Download 30-day Free Trial.
> Pricing starts from $795 for 25 servers or applications!
> http://p.sf.net/sfu/zoho_dev2dev_nov
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
|
