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
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
|
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 <boydb@midnightdesign.ws>) id 1WOWEd-0000uU-PF
for bitcoin-development@lists.sourceforge.net;
Fri, 14 Mar 2014 17:49:31 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of
midnightdesign.ws designates 50.87.144.70 as permitted sender)
client-ip=50.87.144.70; envelope-from=boydb@midnightdesign.ws;
helo=gator3054.hostgator.com;
Received: from gator3054.hostgator.com ([50.87.144.70])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256)
(Exim 4.76) id 1WOWEc-00010Y-NX
for bitcoin-development@lists.sourceforge.net;
Fri, 14 Mar 2014 17:49:31 +0000
Received: from [209.85.212.180] (port=45730 helo=mail-wi0-f180.google.com)
by gator3054.hostgator.com with esmtpsa (TLSv1:RC4-SHA:128)
(Exim 4.80.1) (envelope-from <boydb@midnightdesign.ws>)
id 1WOWEW-0001y2-A0 for bitcoin-development@lists.sourceforge.net;
Fri, 14 Mar 2014 12:49:24 -0500
Received: by mail-wi0-f180.google.com with SMTP id hn9so873148wib.1
for <bitcoin-development@lists.sourceforge.net>;
Fri, 14 Mar 2014 10:49:19 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:mime-version:in-reply-to:references:date
:message-id:subject:from:to:content-type;
bh=Fil55dbXICgKlRJNIvk+1gOfQeZoQdISp7mNmtAtbbQ=;
b=cMUUAoBz2rj/HfU4Bcgl6WVgL3EMe6i6oWIzcyHsQfdXvgIZswxOqtJMYvOzTRJ+PI
Ji1NjjdEqHykNWS9lMIPQSG60bAOCsmAj9XPrEm3rIIMiPaH4ukNoDO3iG0vUbqk2VCV
8USb1Udr2Amo6VsRN9TAEbuCFvulC7uj3DXy34MZUcEC/liTfxcVdBUc6T7SRy+SwRSZ
BZygXJI9nenV+CT8kBwS7CoD8qultfqlHaC5f7PiHRl+C68qn+MeL8EMF7JUeZfU5A+7
XDvE+q5EI94KTBq0x36apioM4L8niO6wVX68K1A8+OaQVhDYHmoqcvpamwo3L3V55OHS
hM6A==
X-Gm-Message-State: ALoCoQn16JhcC+Wx4q9b97HSmCIETcA6+RCHAE+C5MlA7orsNP7sQ28a5mymUfOn5z/6EsAv+W0T
MIME-Version: 1.0
X-Received: by 10.180.98.232 with SMTP id el8mr3160783wib.27.1394819359836;
Fri, 14 Mar 2014 10:49:19 -0700 (PDT)
Received: by 10.227.71.71 with HTTP; Fri, 14 Mar 2014 10:49:19 -0700 (PDT)
In-Reply-To: <CAMPt2UN=ySXRP04cB+Cx3frF0u9F2yWoHCVZsvz5VG=ZEaZJCw@mail.gmail.com>
References: <CAMPt2UN=ySXRP04cB+Cx3frF0u9F2yWoHCVZsvz5VG=ZEaZJCw@mail.gmail.com>
Date: Fri, 14 Mar 2014 12:49:19 -0500
Message-ID: <CANg-TZB3snv+ny5NdwMic_NtSbMCvt_=qSViJHXeTsdU2Qnygg@mail.gmail.com>
From: Brooks Boyd <boydb@midnightdesign.ws>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Content-Type: multipart/alternative; boundary=f46d0442885e78258004f494b079
X-AntiAbuse: This header was added to track abuse,
please include it with any abuse report
X-AntiAbuse: Primary Hostname - gator3054.hostgator.com
X-AntiAbuse: Original Domain - lists.sourceforge.net
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - midnightdesign.ws
X-BWhitelist: no
X-Source-IP: 209.85.212.180
X-Source:
X-Source-Args:
X-Source-Dir:
X-Source-Sender: (mail-wi0-f180.google.com) [209.85.212.180]:45730
X-Source-Auth: midnight
X-Email-Count: 1
X-Source-Cap: bWlkbmlnaHQ7bWlkbmlnaHQ7Z2F0b3IzMDU0Lmhvc3RnYXRvci5jb20=
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 SPF_HELO_PASS SPF: HELO matches SPF record
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
X-Headers-End: 1WOWEc-00010Y-NX
Subject: Re: [Bitcoin-development] Physical key / edge detection software
and PIN to generate private key
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: Fri, 14 Mar 2014 17:49:31 -0000
--f46d0442885e78258004f494b079
Content-Type: text/plain; charset=ISO-8859-1
On Thu, Mar 13, 2014 at 9:38 PM, Jack Scott <jack.scott.public@gmail.com>wrote:
> BIP: XX
> Title: Physical key / edge detection software and PIN to generate a
> Bitcoin private key
> Author: Jack Scott
> Status: Idea
> Type: Standard Track
> Created: 13-3-2014
>
> Abstract:
> A method is proposed to generate a Bitcoin private key by using a physical
> key in conjunction with image recognition software and a PIN. Use edge
> detection software applied to incoming video feed to convert the shape of a
> physical key into an equation that describes the key. The hash of the
> key's equation plus a user generated five digit pin can then be used to
> create a Bitcoin private key.
>
>
Interesting idea, though as Wladimir mentioned, a real-world "key" is much
less secure than a Bitcoin/PGP "key", though in this case, I could see your
physical/visual "key" being any complex, high-contrast image (like a Motion
Tracking Target: https://www.google.com/search?q=tracking+markers&tbm=isch),
if just using edge-detection (a high-contrast image would help make
low-light or out-of-focus shots still able to be detected), though like a
QR-code, it should probably have calibration markers in the corners to
specify orientation (would help decoding a skewed or rotated image) and the
standard should enforce some minimum level of complexity to prevent really
simple and easy-to-reproduce/steal keys .
Though if you're getting to that level of complexity, you might as well
just have a QR code of the private key.
Brooks
--f46d0442885e78258004f494b079
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">On Thu, Mar 13, 2014 at 9:38 PM, Jack Scott <span dir=3D"ltr"><<=
a href=3D"mailto:jack.scott.public@gmail.com" target=3D"_blank">jack.scott.=
public@gmail.com</a>></span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex"><div dir=3D"ltr">BIP: XX<div>Title: Physical key / edge de=
tection software and PIN to generate a Bitcoin private key</div>
<div>Author: Jack Scott</div><div>Status: Idea</div><div>Type: Standard Tra=
ck</div><div>Created: 13-3-2014</div>
<div><br></div><div>Abstract:</div><div>A method is proposed to generate a =
Bitcoin private key by using a physical key in conjunction with image recog=
nition software and a PIN. =A0Use edge detection software applied to incomi=
ng video feed to convert the shape of a physical key into an equation that =
describes the key. =A0The hash of the key's equation plus a user genera=
ted five digit pin can then be used to create a Bitcoin private key.</div>
</div>
<br></blockquote><div><br></div><div>Interesting idea, though as Wladimir m=
entioned, a real-world "key" is much less secure than a Bitcoin/P=
GP "key", though in this case, I could see your physical/visual &=
quot;key" being any complex, high-contrast image (like a Motion Tracki=
ng Target: <a href=3D"https://www.google.com/search?q=3Dtracking+markers&am=
p;tbm=3Disch">https://www.google.com/search?q=3Dtracking+markers&tbm=3D=
isch</a>), if just using edge-detection (a high-contrast image would help m=
ake low-light or out-of-focus shots still able to be detected), though like=
a QR-code, it should probably have calibration markers in the corners to s=
pecify orientation (would help decoding a skewed or rotated image) and the =
standard should enforce some minimum level of complexity to prevent really =
simple and easy-to-reproduce/steal keys .</div>
<div><br></div><div>Though if you're getting to that level of complexit=
y, you might as well just have a QR code of the private key.</div><div><br>=
</div><div>Brooks</div></div></div></div>
--f46d0442885e78258004f494b079--
|
