From mboxrd@z Thu Jan 1 00:00:00 1970 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 1WQi3H-0004ym-GV for bitcoin-development@lists.sourceforge.net; Thu, 20 Mar 2014 18:50:51 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.128.169 as permitted sender) client-ip=209.85.128.169; envelope-from=alexy.kot.all@gmail.com; helo=mail-ve0-f169.google.com; Received: from mail-ve0-f169.google.com ([209.85.128.169]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1WQi3E-0002M2-98 for bitcoin-development@lists.sourceforge.net; Thu, 20 Mar 2014 18:50:51 +0000 Received: by mail-ve0-f169.google.com with SMTP id pa12so1440755veb.14 for ; Thu, 20 Mar 2014 11:50:42 -0700 (PDT) X-Received: by 10.220.81.194 with SMTP id y2mr5653608vck.29.1395341442693; Thu, 20 Mar 2014 11:50:42 -0700 (PDT) MIME-Version: 1.0 Sender: alexy.kot.all@gmail.com Received: by 10.59.0.38 with HTTP; Thu, 20 Mar 2014 11:50:02 -0700 (PDT) In-Reply-To: References: From: Alex Kotenko Date: Thu, 20 Mar 2014 18:50:02 +0000 X-Google-Sender-Auth: WS8mNhEO1B7isNQP2WpS_bdlp8A Message-ID: To: Mike Hearn Content-Type: multipart/alternative; boundary=001a11c2d8600852da04f50e3f98 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 (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.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: 1WQi3E-0002M2-98 Cc: Bitcoin Dev , Andreas Schildbach Subject: Re: [Bitcoin-development] Payment Protocol for Face-to-face Payments 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: Thu, 20 Mar 2014 18:50:51 -0000 --001a11c2d8600852da04f50e3f98 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable We'll see how it will go, maybe I will get to implement this somewhere soon= . Yes, I'm thinking exactly about radio MitM attacks possible with bluetooth. I'll also look into using PKI inside the PoS for the merchant. It would be great user experience if we would be able to provide a signed payment request with human recognizable merchant identity name in the way you described much earlier in Bitcoin 0.9 FAQ. =E2=80=8B 2014-03-20 18:31 GMT+00:00 Mike Hearn : > With Java, in theory, you can use SSLSocketFactory.createSocket(btsocket, > address, 1234, true) to wrap a bluetooth socket in SSL. However I have no= t > tried it. > > For now, just prototype and build your product without the security. We > can find someone to experiment with this, if you don't want to . > > Bluetooth needs encryption and MACs as well as signing to be secure, > because there could be radio MITM. Yes, this overlaps somewhat with the P= KI > signing in BIP70, but not entirely - you might want to serve unsigned > payment requests, but still have confidentiality and authenticity for a > local face to face transaction. The signing and encryption does different > things. > > > On Thu, Mar 20, 2014 at 7:20 PM, Alex Kotenko wrote: > >> Hmm, is there any other way to do it? Can we provide a signed payment >> request and verify the sign on receiving side and this way protect from >> bluetooth MitM attack? Quick googling showed that SSL over bluetooth isn= 't >> a very well developed area, and my own skills are not enough to quickly >> implement a reliable secure solution here. >> >> >> 2014-03-20 10:36 GMT+00:00 Mike Hearn : >> >>> Encoding entire payment requests into qrcodes is definitely not the way >>> to go. They can already be large when signed and we're just at the star= t of >>> adding features. >>> >>> Finishing off and standardising the bluetooth support is the way to go >>> (r=3Dbt:mac). Andreas' app already has some support for this I believe,= so >>> Alex you could prototype with that, but we need to: >>> >>> 1) Add an encryption/auth layer on top, because it runs over RFCOMM >>> sockets. The authentication would require proof of owning the Bitcoin k= ey >>> that's in the address part of the URI (which is needed for backwards co= mpat >>> anyway). >>> >>> 2) Write a BIP for it and make sure it's interoperable >>> >>> For the auth layer we could either use SSL and then just ignore the >>> server certificate and require signing of the session public key with t= he >>> Bitcoin key, which should be easy to code up but is rather heavy on the >>> air, or roll a custom lightweight thing where we just do a basic ECDH, = with >>> the servers key being the same as the address key. But rolling such >>> protocols is subtle and I guess it'd need to be reviewed by people fami= liar >>> with such things. >>> >>> This feels like a good opportunity to grow the community - perhaps we >>> can find a volunteer in the forums who enjoys crypto. >>> >>> >>> -----------------------------------------------------------------------= ------- >>> Learn Graph Databases - Download FREE O'Reilly Book >>> "Graph Databases" is the definitive new guide to graph databases and >>> their >>> applications. Written by three acclaimed leaders in the field, >>> this first edition is now available. Download your free book today! >>> http://p.sf.net/sfu/13534_NeoTech >>> _______________________________________________ >>> Bitcoin-development mailing list >>> Bitcoin-development@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/bitcoin-development >>> >>> >> > --001a11c2d8600852da04f50e3f98 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
We'll see how it will go, maybe I will get= to implement this somewhere soon.

Yes, I'm thinking exactly about radio MitM attack= s possible with bluetooth. I'll also look into using PKI inside the PoS= for the merchant. It would be great user experience if we would be able to= provide a signed payment request with human recognizable merchant identity= name in the way you described much earlier in Bitcoin 0.9 FAQ. =E2=80=8B


2014-03-20 18:31 GMT+00:00 Mike Hearn <mike@plan99.net>:
With Java, in theory, you c= an use SSLSocketFactory.createSocket(btsocket, address, 1234, true) to wrap= a bluetooth socket in SSL. However I have not tried it.

For now, just prototype and build your product without the s= ecurity. We can find someone to experiment with this, if you don't want= to .

Bluetooth needs encryption and MACs as well as signing = to be secure, because there could be radio MITM. Yes, this overlaps somewha= t with the PKI signing in BIP70, but not entirely - you might want to serve= unsigned payment requests, but still have confidentiality and authenticity= for a local face to face transaction. The signing and encryption does diff= erent things.

On Thu, Mar 20, 2014 at 7:20 PM, Alex Kote= nko <alexykot@gmail.com> wrote:
Hmm, is there any other way to do it? C= an we provide a signed payment request and verify the sign on receiving sid= e and this way protect from bluetooth MitM attack? Quick googling showed th= at SSL over bluetooth isn't a very well developed area, and my own skil= ls are not enough to quickly implement a reliable secure solution here.


<= div class=3D"gmail_extra">
2014-03-20 10:36 GMT+0= 0:00 Mike Hearn <mike@plan99.net>:
Encoding entire payment requests into qrcodes is definitely not t= he way to go. They can already be large when signed and we're just at t= he start of adding features.

Finishing off and standardising the bl= uetooth support is the way to go (r=3Dbt:mac). Andreas' app already has= some support for this I believe, so Alex you could prototype with that, bu= t we need to:

1) Add an e= ncryption/auth layer on top, because it runs over RFCOMM sockets. The authe= ntication would require proof of owning the Bitcoin key that's in the a= ddress part of the URI (which is needed for backwards compat anyway).

2) Write a = BIP for it and make sure it's interoperable

For the auth layer we could eithe= r use SSL and then just ignore the server certificate and require signing o= f the session public key with the Bitcoin key, which should be easy to code= up but is rather heavy on the air, or roll a custom lightweight thing wher= e we just do a basic ECDH, with the servers key being the same as the addre= ss key. But rolling such protocols is subtle and I guess it'd need to b= e reviewed by people familiar with such things.

This feels = like a good opportunity to grow the community - perhaps we can find a volun= teer in the forums who enjoys crypto.

------------------------------------------------------= ------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases = and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf= .net/sfu/13534_NeoTech
_____________________________________________= __
Bitcoin-development mailing list
Bitcoin-development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bitcoin-de= velopment




--001a11c2d8600852da04f50e3f98--