{"type":"rich","version":"1.0","author_name":"npub1assqju94qjdpunps2yck2vtzfhnme5pclv0aantfajkjs5w2057quzu5p3","author_url":"https://nostr.ae/npub1assqju94qjdpunps2yck2vtzfhnme5pclv0aantfajkjs5w2057quzu5p3","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2014-03-08\n📝 Original message:On 8 March 2014 17:10, Alan Reiner \u003cetotheipi at gmail.com\u003e wrote:\n\n\n\u003e I create a new keypair, \u003cc_pub\u003e with \u003cc_priv\u003e which I know (it can be any\n\u003e arbitrary key pair).  But I don't give you \u003cc_pub\u003e, I give you  \u003cb_pub\u003e =\n\u003e \u003cc_pub\u003e minus \u003ca_pub\u003e (which I can do because I've seen \u003ca_pub\u003e before\n\u003e doing this).\n\u003e\n\u003e Sure, I don't know the private key for \u003cb_pub\u003e, but it doesn't matter...\n\u003e because what\n\u003e\n\u003e \u003cb_pub\u003e + \u003ca_pub\u003e = \u003cc_pub\u003e (mine)\n\u003e\n\u003e You have no way to detect this condition, because you don't know what\n\u003e c_pub/c_priv I created, so you can only detect this after it's too late\n\u003e (after I abuse the private key)\n\u003e\n\nThanks Alan and Forrest, that makes sense. So to salvage the situation in\nthe original case, we have to make sure the parties exchange their public\nkeys first, before they're allowed to see the public keys they'll be\ncombining them with.\n\n-- \n-- \nEdmund Edgar\nFounder, Social Minds Inc (KK)\nTwitter: @edmundedgar\nLinked In: edmundedgar\nSkype: edmundedgar\nhttp://www.socialminds.jp\n\nReality Keys\n@realitykeys\ned at realitykeys.com\nhttps://www.realitykeys.com\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20140308/ef8e3571/attachment.html\u003e"}