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
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <laanwj@gmail.com>) id 1WOIfC-0006D6-GU
for bitcoin-development@lists.sourceforge.net;
Fri, 14 Mar 2014 03:20:02 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.213.169 as permitted sender)
client-ip=209.85.213.169; envelope-from=laanwj@gmail.com;
helo=mail-ig0-f169.google.com;
Received: from mail-ig0-f169.google.com ([209.85.213.169])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1WOIfB-00051M-Nr
for bitcoin-development@lists.sourceforge.net;
Fri, 14 Mar 2014 03:20:02 +0000
Received: by mail-ig0-f169.google.com with SMTP id h18so411440igc.0
for <bitcoin-development@lists.sourceforge.net>;
Thu, 13 Mar 2014 20:19:56 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.42.114.82 with SMTP id f18mr42553icq.56.1394767196381; Thu,
13 Mar 2014 20:19:56 -0700 (PDT)
Received: by 10.64.27.34 with HTTP; Thu, 13 Mar 2014 20:19:56 -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 04:19:56 +0100
Message-ID: <CA+s+GJB5bh3W1kkNQ78Xyds+o4x84eDc=OUFFb3gzZzDrEC+ag@mail.gmail.com>
From: Wladimir <laanwj@gmail.com>
To: Jack Scott <jack.scott.public@gmail.com>
Content-Type: multipart/alternative; boundary=20cf303f6dce48ebdb04f4888b78
X-Spam-Score: -0.6 (/)
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
(laanwj[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: 1WOIfB-00051M-Nr
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
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 03:20:02 -0000
--20cf303f6dce48ebdb04f4888b78
Content-Type: text/plain; charset=UTF-8
On Fri, Mar 14, 2014 at 3:38 AM, Jack Scott <jack.scott.public@gmail.com>wrote:
> 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.
>
Some practical nits:
- Physical keys are vulnerable to photography-based reproduction attacks.
That gets even worse if you use them to identify to a digital system as you
can leave out the tiresome manual reproduction step.
- The output from computer vision algorithms is notoriously noisy. If you
use that as input for hashing a private key, it may become hard/impossible
to reproduce (also, physical objects may deform over time).
Wladimir
--20cf303f6dce48ebdb04f4888b78
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">On F=
ri, Mar 14, 2014 at 3:38 AM, Jack Scott <span dir=3D"ltr"><<a href=3D"ma=
ilto: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:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div>A method is proposed t=
o generate a Bitcoin private key by using a physical key in conjunction wit=
h image recognition software and a PIN. =C2=A0Use edge detection software a=
pplied to incoming video feed to convert the shape of a physical key into a=
n equation that describes the key. =C2=A0The hash of the key's equation=
plus a user generated five digit pin can then be used to create a Bitcoin =
private key.</div>
</div></blockquote><div><br></div><div>Some practical nits:</div><div><br><=
/div><div>- Physical keys are vulnerable to photography-based reproduction =
attacks. That gets even worse if you use them to identify to a digital syst=
em as you can leave out the tiresome manual reproduction step.</div>
<div><br></div><div>- The output from computer vision algorithms is notorio=
usly noisy. If you use that as input for hashing a private key, it may beco=
me hard/impossible to reproduce (also, physical objects may deform over tim=
e).</div>
<div><br></div><div>Wladimir</div><div><br></div></div></div></div>
--20cf303f6dce48ebdb04f4888b78--
|
