From: Brooks Boyd <boydb@midnightdesign•ws>
To: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Paper Currency
Date: Mon, 19 May 2014 08:06:40 -0500 [thread overview]
Message-ID: <CANg-TZAFdmPBj_+U=jbhP_t9Gb-yZ-8LMtGzj+6ub=qWcLP0UQ@mail.gmail.com> (raw)
In-Reply-To: <CALDj+BaQ5sn9_=KAmNUUbmDva2g3mabm_wmcL_gibLyci5zFUQ@mail.gmail.com>
>> 2014-05-18 13:14 GMT+01:00 Andreas Schildbach <andreas@schildbach•de>:
>> 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.
>
>On Sun, May 18, 2014 at 7:51 AM, Alex Kotenko <alexykot@gmail•com> wrote:
>
> 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
One thought I had reading through this exchange: I think the general
public is becoming more aware of the "hacker with a long range
antenna" sort of attack, since credit cards are getting microchips
that can be scanned. There's a few videos I've seen of white hat
hackers demonstrating how a suitcase-sized apparatus carried by
someone walking down the street can scan and make charges on cards in
people's pockets as the attacker brushes past. Hence RFID-blocking
sleeves/wallets are on the market, such that your smart credit card
can't make a purchase while its in your wallet. Is a RFID-blocking
wallet also NFC-blocking? Irregardless of whatever "future cash" you
choose to carry (be it credit card or bitcoin card/coin/cash), perhaps
its the wallet/purse that needs an upgrade, to ensure your money
doesn't spend itself while its in your pocket, but you can easily
remove it and spend it conveniently?
Brooks
next prev parent reply other threads:[~2014-05-19 13:39 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-17 15:31 Jerry Felix
2014-05-17 15:45 ` Matt Whitlock
2014-05-17 16:07 ` Chris Pacia
2014-05-17 16:40 ` Gregory Maxwell
2014-05-18 11:47 ` Alex Kotenko
2014-05-18 12:14 ` Andreas Schildbach
2014-05-18 12:51 ` Alex Kotenko
2014-05-19 13:06 ` Brooks Boyd [this message]
2014-05-19 13:50 ` Alex Kotenko
2014-05-18 13:50 ` Natanael
2014-05-18 18:47 ` Alex Kotenko
2014-05-18 20:10 ` Natanael
2014-05-19 10:26 ` Alex Kotenko
2014-05-19 12:55 ` Sergio Lerner
2014-05-19 13:34 ` Martin Sip
2014-05-19 13:53 ` Alex Kotenko
2014-05-19 14:47 ` [Bitcoin-development] patents Adam Back
2014-05-19 15:09 ` Mike Hearn
2014-05-19 18:27 ` Peter Todd
2014-05-19 18:40 ` Mike Hearn
2014-05-19 18:43 ` Gregory Maxwell
2014-05-19 18:46 ` Peter Todd
2014-05-19 18:49 ` Mike Hearn
2014-05-19 22:15 ` Bernd Jendrissek
2014-05-20 10:30 ` Jeff Garzik
2014-05-18 13:50 ` [Bitcoin-development] Paper Currency Andreas Schildbach
2014-05-19 12:21 ` Mike Hearn
2014-05-19 18:20 ` Justus Ranvier
2014-05-19 18:39 ` Peter Todd
2014-05-18 19:54 Jerry Felix
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='CANg-TZAFdmPBj_+U=jbhP_t9Gb-yZ-8LMtGzj+6ub=qWcLP0UQ@mail.gmail.com' \
--to=boydb@midnightdesign$(echo .)ws \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/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