Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Wm0a4-0008A0-QA for bitcoin-development@lists.sourceforge.net; Sun, 18 May 2014 12:52:44 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.220.174 as permitted sender) client-ip=209.85.220.174; envelope-from=alexy.kot.all@gmail.com; helo=mail-vc0-f174.google.com; Received: from mail-vc0-f174.google.com ([209.85.220.174]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1Wm0a3-0007sy-Lp for bitcoin-development@lists.sourceforge.net; Sun, 18 May 2014 12:52:44 +0000 Received: by mail-vc0-f174.google.com with SMTP id lh14so8253456vcb.5 for ; Sun, 18 May 2014 05:52:38 -0700 (PDT) X-Received: by 10.58.181.202 with SMTP id dy10mr19649594vec.3.1400417558164; Sun, 18 May 2014 05:52:38 -0700 (PDT) MIME-Version: 1.0 Sender: alexy.kot.all@gmail.com Received: by 10.58.211.135 with HTTP; Sun, 18 May 2014 05:51:57 -0700 (PDT) In-Reply-To: References: <5377892C.8080402@gmail.com> From: Alex Kotenko Date: Sun, 18 May 2014 13:51:57 +0100 X-Google-Sender-Auth: 2I9nmeV6k3EMgMNN7ixPYH3K9zI Message-ID: To: Andreas Schildbach Content-Type: multipart/alternative; boundary=047d7b673772177a0504f9ac1f1f X-Spam-Score: -0.3 (/) 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 (alexy.kot.all[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 1.0 HTML_MESSAGE BODY: HTML included in message 0.3 HTML_FONT_FACE_BAD BODY: HTML font face is not a word -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: 1Wm0a3-0007sy-Lp Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] Paper Currency X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 May 2014 12:52:45 -0000 --047d7b673772177a0504f9ac1f1f Content-Type: text/plain; charset=UTF-8 Yes, but it must not sacrifice usability. It's paper money, people are used to it and they have rather high standard of expectations in this area. Any usbility sacrifices in this area result into failure of the whole thing. Best regards, Alex Kotenko 2014-05-18 13:14 GMT+01:00 Andreas Schildbach : > > One problem we couldn't figure out here though - how to protect the > > notes from unauthorized redeem. Like if someone else tries to reach your > > wallet with his own NFC - how can we distinguish between deliberate > > redeem by owner and fraudulent redeem by anybody else with custom built > > long range NFC antenna? Any ideas? > > I think you'd need multiple factors to protect against that attack. Like > encrypting with a key that is printed on the note as an QR code. > > > > > ------------------------------------------------------------------------------ > "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE > Instantly run your Selenium tests across 300+ browser/OS combos. > Get unparalleled scalability from the best Selenium testing platform > available > Simple to use. Nothing to install. Get started now for free." > http://p.sf.net/sfu/SauceLabs > _______________________________________________ > Bitcoin-development mailing list > Bitcoin-development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bitcoin-development > --047d7b673772177a0504f9ac1f1f Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Yes, but it must not sacrifice usability. It&#= 39;s paper money, people are used to it and they have rather high standard = of expectations in this area. Any usbility sacrifices in this area result i= nto failure of the whole thing.

Best regards,=C2=A0
Alex Kotenko


2014-05-18 13:14 GMT+01:00 Andreas Schil= dbach <andreas@schildbach.de>:
> One problem we couldn't figure out here though - h= ow to protect the
> notes from unauthorized redeem. Like if someone else tries to reach yo= ur
> wallet with his own NFC - how can we distinguish between deliberate > redeem by owner and fraudulent redeem by anybody else with custom buil= t
> long range NFC antenna? Any ideas?

I think you'd need multiple factors to protect against that attac= k. Like
encrypting with a key that is printed on the note as an QR code.



---------------------------------------------------------------------------= ---
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE=
Instantly run your Selenium tests across 300+ browser/OS combos.
Get unparalleled scalability from the best Selenium testing platform availa= ble
Simple to use. Nothing to install. Get started now for free."
http://p.sf.net= /sfu/SauceLabs
_______________________________________________
Bitcoin-development mailing list
Bitcoin-develo= pment@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bitcoin-de= velopment

--047d7b673772177a0504f9ac1f1f--