From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id DF702514 for ; Thu, 23 Jul 2015 00:07:04 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.7.6 Received: from mail-pa0-f43.google.com (mail-pa0-f43.google.com [209.85.220.43]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 3A0F2161 for ; Thu, 23 Jul 2015 00:07:04 +0000 (UTC) Received: by pachj5 with SMTP id hj5so146510307pac.3 for ; Wed, 22 Jul 2015 17:07:03 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type; bh=8dEKtSd97grNfSSRB/W126cQsDD+z+ZsWCJccsCYU6M=; b=hFpWtuk4TsLGu6cfGwHhPFnFWkgwE6Qf+qRLehtOuwba1x/HutHZo3F9tiIY/m/aLR 79ri6zca08MlBWZl1B6uc6BjOf4fb/YqQfNSXv3FAGEsHGw8rBsN34NJaNUkTW4EwAX5 fRG07uxGJSud/s8KPiAXgu6dFJzozJmq9yscaeBbYAdyGZ/0O/jQ0XskYWZCK6TMn0ri WtjEm8U95Oy+VH4XQmLvh50zqwQqHWTGAA3LcQJptw6s6A5I811VtIsbwVgs6ni1X+tX YbhzUdVkK6HpDJbqzzFA4rPTSiyMC1RVuZxT03LiDWbSrSBKStATsgO2jbo6sAxyjd8U C8+A== X-Gm-Message-State: ALoCoQlY3c8isl49419kuEeThV4f6zXlw3hDRkSfuu++VRClci55X8oWb7wxpnHQFH3ldJJWvVjN X-Received: by 10.70.23.196 with SMTP id o4mr11652650pdf.164.1437610023816; Wed, 22 Jul 2015 17:07:03 -0700 (PDT) Received: from [10.0.1.14] (c-67-161-88-20.hsd1.wa.comcast.net. [67.161.88.20]) by smtp.googlemail.com with ESMTPSA id t2sm5305803pdo.81.2015.07.22.17.07.02 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 22 Jul 2015 17:07:03 -0700 (PDT) Message-ID: <55B03032.5020306@voskuil.org> Date: Wed, 22 Jul 2015 17:07:14 -0700 From: Eric Voskuil User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: gb , Thomas Voegtlin References: <55AFBBE6.3060702@electrum.org> <1437606706.2688.0.camel@yahoo.com> In-Reply-To: <1437606706.2688.0.camel@yahoo.com> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="6rSgkx4iBlV13SeqcAlb9S1tnpHxrf2CA" X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.linux-foundation.org Cc: bitcoin-dev@lists.linuxfoundation.org Subject: Re: [bitcoin-dev] Making Electrum more anonymous X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Bitcoin Development Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Jul 2015 00:07:05 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --6rSgkx4iBlV13SeqcAlb9S1tnpHxrf2CA Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable This is a good point. I didn't delve into the specifics of implementation due to the larger issues that I raised. Libbitcoin Server uses CurveZMQ, an implementation of CurveCP. http://curvecp.org http://curvezmq.org https://en.bitcoin.it/wiki/Libbitcoin_Server e On 07/22/2015 04:11 PM, gb via bitcoin-dev wrote: > Why RSA? >=20 >> >> Here is an idea, inspired by TOR, on which I would like to have some >> feedback: We create an anonymous routing layer between Electrum server= s >> and clients. >> >> * Each server S publishes a RSA public key, KS >> * Each client receives a list of available servers and their pubkeys >> * For each wallet address, addr_i, a client chooses a server S_i, and = a >> RSA keypair (K_addr_i, k_addr_i) >> * The client creates a list of encrypted requests. Each request contai= ns >> addr_i and K_addr_i, and is encrypted with the pubkey KS_i of S_i >> * The client chooses a main server M, and sends the list of encrypted >> requests to M >> * M dispatches the client's requests to the corresponding servers S_i >> (without the client's IP address.) >> * Each server decrypts the requests it receives, performs the request,= >> and encrypts the result with K_addr_i >> * M receives encrypted responses, and forwards them to the client. >> * The client decrypts the encrypted response with k_addr_i --6rSgkx4iBlV13SeqcAlb9S1tnpHxrf2CA Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJVsDAzAAoJEDzYwH8LXOFOoWQH/3rKskYOpSeihm9lP42pDwkX gJtrVawkwCco5YFhm8E68V9JowXlmajJDeaH+P1Y6ma/Lhq4IBer2tUI+/Sr9KEp Liwa4TvqEcjAW8wR9frRGIQgxeuJKntFRGSIi5qrDpsJI2eHZCRgWG/hWx7op0I/ K7wZa4OtwfRaVDFFkFH/af9qeFr3oiKiqhdUO6O9zUf7USLb811oxD0JEQtdeG1c 7hqZT0GmU2MSzpd9yPS8se+ob9PvK6VGeHxq7z9McBY8ZqccqhkBQ6sjQBtHn8z3 lBWFudqKRXIHGU/Hw6yx+MY/rA6eNYdwpNQuqF1cW71pAi82g/ss4D7jvWQ7960= =ooug -----END PGP SIGNATURE----- --6rSgkx4iBlV13SeqcAlb9S1tnpHxrf2CA--