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
117
118
119
120
121
122
123
124
125
126
127
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <allen.piscitello@gmail.com>) id 1Vcmcl-0006om-QP
for bitcoin-development@lists.sourceforge.net;
Sun, 03 Nov 2013 01:37:07 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.212.169 as permitted sender)
client-ip=209.85.212.169;
envelope-from=allen.piscitello@gmail.com;
helo=mail-wi0-f169.google.com;
Received: from mail-wi0-f169.google.com ([209.85.212.169])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Vcmck-0005Iw-02
for bitcoin-development@lists.sourceforge.net;
Sun, 03 Nov 2013 01:37:07 +0000
Received: by mail-wi0-f169.google.com with SMTP id cb5so680817wib.0
for <bitcoin-development@lists.sourceforge.net>;
Sat, 02 Nov 2013 18:36:59 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.180.221.38 with SMTP id qb6mr6985953wic.8.1383442619794;
Sat, 02 Nov 2013 18:36:59 -0700 (PDT)
Received: by 10.194.85.112 with HTTP; Sat, 2 Nov 2013 18:36:59 -0700 (PDT)
In-Reply-To: <201311030127.43010.luke@dashjr.org>
References: <20131102050144.5850@gmx.com> <201311030033.56983.luke@dashjr.org>
<CAJfRnm6eRRF1ZxRJ89enPNkaG3-BNyboP9DujmuBgQxNhdhU8g@mail.gmail.com>
<201311030127.43010.luke@dashjr.org>
Date: Sat, 2 Nov 2013 20:36:59 -0500
Message-ID: <CAJfRnm6_Q2Meoc1wu7Ppa1BpaZQuhdHP5uxZO3UtKppkDXVdWA@mail.gmail.com>
From: Allen Piscitello <allen.piscitello@gmail.com>
To: Luke-Jr <luke@dashjr.org>
Content-Type: multipart/alternative; boundary=001a1134d2daeb8c9204ea3bd5e5
X-Spam-Score: -0.6 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was blocked.
See
http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block
for more information. [URIs: dashjr.org]
-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
(allen.piscitello[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
author's domain
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: 1Vcmck-0005Iw-02
Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Message Signing based authentication
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, 03 Nov 2013 01:37:08 -0000
--001a1134d2daeb8c9204ea3bd5e5
Content-Type: text/plain; charset=ISO-8859-1
Required vs. strongly recommended is an important distinction. Satoshi
Dice reuses EC Keys for every single transaction. Exchanges will have the
same address you deposit in over and over, which gets reused. This is a
best practice argument rather than a protocol requirement.
On Sat, Nov 2, 2013 at 8:27 PM, Luke-Jr <luke@dashjr.org> wrote:
> On Sunday, November 03, 2013 1:19:51 AM Allen Piscitello wrote:
> > I actually had a use case in my case where it was possible, and that was
> > the check I used to get around it, just configured it so that I always
> > generated a new key when I needed to set up a 2 of 2 Multisig Refund Tx.
> > It was either that or making sure I had no unspent outputs. The use
> case
> > of doing it was laziness in just creating a single key.
>
> Use cases mean an actual use, not mere laziness. Bitcoin as a system has
> always required a unique EC key (and address) for each transaction.
>
> Luke
>
--001a1134d2daeb8c9204ea3bd5e5
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">Required vs. strongly recommended is an important distinct=
ion. =A0Satoshi Dice reuses EC Keys for every single transaction. =A0Exchan=
ges will have the same address you deposit in over and over, which gets reu=
sed. =A0This is a best practice argument rather than a protocol requirement=
.</div>
<div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Sat, Nov 2=
, 2013 at 8:27 PM, Luke-Jr <span dir=3D"ltr"><<a href=3D"mailto:luke@das=
hjr.org" target=3D"_blank">luke@dashjr.org</a>></span> wrote:<br><blockq=
uote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc =
solid;padding-left:1ex">
<div class=3D"im">On Sunday, November 03, 2013 1:19:51 AM Allen Piscitello =
wrote:<br>
> I actually had a use case in my case where it was possible, and that w=
as<br>
> the check I used to get around it, just configured it so that I always=
<br>
> generated a new key when I needed to set up a 2 of 2 Multisig Refund T=
x.<br>
> =A0It was either that or making sure I had no unspent outputs. =A0The =
use case<br>
> of doing it was laziness in just creating a single key.<br>
<br>
</div>Use cases mean an actual use, not mere laziness. Bitcoin as a system =
has<br>
always required a unique EC key (and address) for each transaction.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
Luke<br>
</font></span></blockquote></div><br></div>
--001a1134d2daeb8c9204ea3bd5e5--
|
