Return-Path: Received: from smtp1.osuosl.org (smtp1.osuosl.org [140.211.166.138]) by lists.linuxfoundation.org (Postfix) with ESMTP id 4853CC002D for ; Tue, 18 Oct 2022 12:42:24 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp1.osuosl.org (Postfix) with ESMTP id 2346B83B07 for ; Tue, 18 Oct 2022 12:42:24 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.11.0 smtp1.osuosl.org 2346B83B07 X-Virus-Scanned: amavisd-new at osuosl.org X-Spam-Flag: NO X-Spam-Score: -0.517 X-Spam-Level: X-Spam-Status: No, score=-0.517 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, KHOP_HELO_FCRDNS=0.399, RDNS_DYNAMIC=0.982, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=no autolearn_force=no Received: from smtp1.osuosl.org ([127.0.0.1]) by localhost (smtp1.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Tdaui1_kmWqe for ; Tue, 18 Oct 2022 12:42:23 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.8.0 DKIM-Filter: OpenDKIM Filter v2.11.0 smtp1.osuosl.org 4812983D13 Received: from mail.wpsoftware.net (s66-183-0-205.bc.hsia.telus.net [66.183.0.205]) by smtp1.osuosl.org (Postfix) with ESMTP id 4812983D13 for ; Tue, 18 Oct 2022 12:42:23 +0000 (UTC) Received: from camus (camus-andrew.lan [192.168.0.190]) by mail.wpsoftware.net (Postfix) with ESMTPSA id CF3D5400EB; Tue, 18 Oct 2022 12:38:49 +0000 (UTC) Date: Tue, 18 Oct 2022 12:42:21 +0000 From: Andrew Poelstra To: Bryan Bishop , Bitcoin Protocol Discussion Message-ID: References: <9f399e0c2713f2b1d2534cd754356bb5@dtrt.org> <1-euAstnYmNT7A9s0rniXdimmudFXODjkXiYXLK1hx1W7f_2rBLD1lPpaNi9Vx9tq2oahdCs6wDuXMy9SR6WfRTYzl2vDxSi6IVQLELKNLs=@protonmail.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="6mwqPiT+S+vSIpQA" Content-Disposition: inline In-Reply-To: Subject: Re: [bitcoin-dev] =?utf-8?q?Trustless_Address_Server_=E2=80=93_Outsou?= =?utf-8?q?rcing_handing_out_addresses_to_prevent_address_reuse?= X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Bitcoin Protocol Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Oct 2022 12:42:24 -0000 --6mwqPiT+S+vSIpQA Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Oct 17, 2022 at 07:07:07PM -0500, Bryan Bishop via bitcoin-dev wrot= e: >=20 > Isn't this the same problem but now for copy-pasting pubkeys instead of an > address? > No, as I understand the proposal, the "public key" held by the wallet is si= mply a signing key used to authenticate addresses, and never leaves the wallet. = Yes, if the wallet's own memory is compromised, it can be tricked into accepting= bad addresses, but this is much much harder than compromising data on the clipb= oard, which basically any application can do without any "real" exploits or speci= al permissions. As an extreme, this proposal could be run on a hardware wallet which had so= me out-of-band way to obtain and authenticate public keys (similar to Signal QR codes). --=20 Andrew Poelstra Director of Research, Blockstream Email: apoelstra at wpsoftware.net Web: https://www.wpsoftware.net/andrew The sun is always shining in space -Justin Lewis-Webster --6mwqPiT+S+vSIpQA Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEkPnKPD7Je+ki35VexYjWPOQbl8EFAmNOnywACgkQxYjWPOQb l8Gvqwf/acmmpIFtX6fkFIO9E5y8irR7PLt9H2EVVwjAqmZ0EbkT8ZMheScwNKQK 1Ga/sEXvmuXKU+mEyD+bwAozKVxa/xE0KYzwfiwsQJYXjXpAdSlIKF8DBuWvAW4r +pb2eSEa4ienCJ7dF8/9YcdxNq2pQjMtvQ0xaBRBHwPZpl4AEyBCPifdjRVBKPWV UjQJNu8udWRA5fNQ9hYavA97e7wPv040EaHeHMzWWSO2EBSqpUYi/tcWbPJpGK6/ gxDUQq/XCAHkri2mqXMQ95yKZF+70g7JggNXtF+WLMGvRCcRVNZlte+Chup5Wolk YIROPwbo98H4Ch2weaMbpGwYp1A5wg== =nYm4 -----END PGP SIGNATURE----- --6mwqPiT+S+vSIpQA--