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 448418B1 for ; Tue, 16 Aug 2016 19:23:59 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from zinan.dashjr.org (unknown [192.3.11.21]) by smtp1.linuxfoundation.org (Postfix) with ESMTP id EEA2A1DA for ; Tue, 16 Aug 2016 19:23:58 +0000 (UTC) Received: from ishibashi.localnet (unknown [IPv6:2001:470:5:265:61b6:56a6:b03d:28d6]) (Authenticated sender: luke-jr) by zinan.dashjr.org (Postfix) with ESMTPSA id AA82038A17C5; Tue, 16 Aug 2016 19:22:32 +0000 (UTC) X-Hashcash: 1:25:160816:bitcoin-dev@lists.linuxfoundation.org::Jvj8mb2tkl1AdMMR:bKt7Z X-Hashcash: 1:25:160816:dev@jonasschnelli.ch::rNBTHhl/mdVEGfOQ:fm5se From: Luke Dashjr To: bitcoin-dev@lists.linuxfoundation.org, Jonas Schnelli Date: Tue, 16 Aug 2016 19:22:29 +0000 User-Agent: KMail/1.13.7 (Linux/4.1.18-gentoo; KDE/4.14.20; x86_64; ; ) References: <57B31EBC.1030806@jonasschnelli.ch> In-Reply-To: <57B31EBC.1030806@jonasschnelli.ch> X-PGP-Key-Fingerprint: E463 A93F 5F31 17EE DE6C 7316 BD02 9424 21F4 889F X-PGP-Key-ID: BD02942421F4889F X-PGP-Keyserver: hkp://pgp.mit.edu MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <201608161922.30588.luke@dashjr.org> X-Spam-Status: No, score=-0.9 required=5.0 tests=BAYES_00,RDNS_DYNAMIC autolearn=no version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.linux-foundation.org Cc: Pavol Rusnak via bitcoin-dev Subject: Re: [bitcoin-dev] Hardware Wallet Standard X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Bitcoin Protocol Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Aug 2016 19:23:59 -0000 On Tuesday, August 16, 2016 2:10:04 PM Jonas Schnelli via bitcoin-dev wrote: > The BIP describes two approaches how to communicate (pipe and > URI-scheme) with the signing-devices app, although, in my opinion, all > major platform do support the URI approach (maybe we could drop the pipe > approach then). IMO it's kindof ugly to abuse URIs for communication. Stdio pipes are pretty universally supported, why not just use those? On the other hand, no matter how the plugin is implemented, it's still a security risk, and requires installation (which the user might not have access for). It would be best if the hardware protocol were standardised, so the user doesn't need a plugin of *any* sort... I notice some hardware wallets have begun to implement (or reuse) Trezor's interface, so that would seem a good place to start? Luke