From: Wladimir <laanwj@gmail•com>
To: Jack Scott <jack.scott.public@gmail•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Physical key / edge detection software and PIN to generate private key
Date: Fri, 14 Mar 2014 04:19:56 +0100 [thread overview]
Message-ID: <CA+s+GJB5bh3W1kkNQ78Xyds+o4x84eDc=OUFFb3gzZzDrEC+ag@mail.gmail.com> (raw)
In-Reply-To: <CAMPt2UN=ySXRP04cB+Cx3frF0u9F2yWoHCVZsvz5VG=ZEaZJCw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 937 bytes --]
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
[-- Attachment #2: Type: text/html, Size: 1376 bytes --]
next prev parent reply other threads:[~2014-03-14 3:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-14 2:38 Jack Scott
2014-03-14 3:19 ` Wladimir [this message]
2014-03-14 17:49 ` Brooks Boyd
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CA+s+GJB5bh3W1kkNQ78Xyds+o4x84eDc=OUFFb3gzZzDrEC+ag@mail.gmail.com' \
--to=laanwj@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=jack.scott.public@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox