rich1.0npub1assqju94qjdpunps2yck2vtzfhnme5pclv0aantfajkjs5w2057quzu5p3https://nostr.ae/npub1assqju94qjdpunps2yck2vtzfhnme5pclv0aantfajkjs5w2057quzu5p3njumphttps://nostr.ae📅 Original date posted:2014-03-08 📝 Original message:On 8 March 2014 17:10, Alan Reiner <etotheipi at gmail.com> wrote: > I create a new keypair, <c_pub> with <c_priv> which I know (it can be any > arbitrary key pair). But I don't give you <c_pub>, I give you <b_pub> = > <c_pub> minus <a_pub> (which I can do because I've seen <a_pub> before > doing this). > > Sure, I don't know the private key for <b_pub>, but it doesn't matter... > because what > > <b_pub> + <a_pub> = <c_pub> (mine) > > You have no way to detect this condition, because you don't know what > c_pub/c_priv I created, so you can only detect this after it's too late > (after I abuse the private key) > Thanks Alan and Forrest, that makes sense. So to salvage the situation in the original case, we have to make sure the parties exchange their public keys first, before they're allowed to see the public keys they'll be combining them with. -- -- Edmund Edgar Founder, Social Minds Inc (KK) Twitter: @edmundedgar Linked In: edmundedgar Skype: edmundedgar http://www.socialminds.jp Reality Keys @realitykeys ed at realitykeys.com https://www.realitykeys.com -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20140308/ef8e3571/attachment.html>