Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1VhqY2-0005FM-N3 for bitcoin-development@lists.sourceforge.net; Sun, 17 Nov 2013 00:49:10 +0000 X-ACL-Warn: Received: from mail-ee0-f49.google.com ([74.125.83.49]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1VhqY1-0008Jy-1L for bitcoin-development@lists.sourceforge.net; Sun, 17 Nov 2013 00:49:10 +0000 Received: by mail-ee0-f49.google.com with SMTP id b47so63823eek.22 for ; Sat, 16 Nov 2013 16:49:02 -0800 (PST) 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 :content-transfer-encoding; bh=DNt0FRxYPNvSktsxaOJ9pzJLwPYB9bbv8YDKm8Yqo/Y=; b=cLg7CkPO/FxM0qcgcQhV1TH/s2pNCkKRjDdnT8F78v60IE5NQ9mcEaQHbcgMaNwfv4 1un8KtpD29qAd19HZgo5gJ9OZVkicjN6d6zuBhrKDjDn2GEjTcJPMWIb1qgfY+7ZMcqg nSnUm0IeY24ghCIOU5Li+K72ZtM1TFBT0TEuA93xzRwgF99wXe1zca4WogLR+vj2yrPV pPe6gOzlpQN3UpZIiquzL4tq9clI5QKOstLEnSVNgM/9PPUX84MH3e0BPqw/uzYrn4Zo rpyhGRKlNrxBetBOE1IaGJVs923RUH2RBJY4f0pv/F0mgqPiNRw1YqgLLRS4GZVykrpI Bo3Q== X-Gm-Message-State: ALoCoQmYWneWs4cYnGMxEbufx9zdmTHRIiGpZYw5QsSxvu3o+sJiimQq7gb9Sds4DGUgNZGV27ws X-Received: by 10.14.179.130 with SMTP id h2mr1896128eem.34.1384649342479; Sat, 16 Nov 2013 16:49:02 -0800 (PST) Received: from tetra.site ([91.239.236.39]) by mx.google.com with ESMTPSA id w6sm21830784eeo.12.2013.11.16.16.49.00 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 16 Nov 2013 16:49:01 -0800 (PST) Message-ID: <5288127C.5010605@gk2.sk> Date: Sun, 17 Nov 2013 01:49:00 +0100 From: Pavol Rusnak User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0 MIME-Version: 1.0 To: timo.hanke@web.de References: <526BDEC2.2090709@gmx.de> <52721F47.30206@gmx.de> <5274C99A.8060304@gmx.de> <20131103064111.GI16611@crunch> <5275F55A.1030805@gmx.de> <20131103074052.GJ16611@crunch> <52880470.2060206@gk2.sk> <20131117004239.GA24383@crunch> In-Reply-To: <20131117004239.GA24383@crunch> X-Enigmail-Version: 1.5.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. 0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [URIs: gk2.sk] X-Headers-End: 1VhqY1-0008Jy-1L Cc: bitcoin-development@lists.sourceforge.net Subject: Re: [Bitcoin-development] Proposal to replace BIP0039 X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Nov 2013 00:49:10 -0000 On 17/11/13 01:42, Timo Hanke wrote: > p.s. The question about auditing entropy would only apply to the generator, > not the wallet. Is it yet documented how Trezor proves that external > entropy was used? We'll probably use the most straightforward way: a) trezor prints entropy A on a display (probably in hex format, this step is triggered by sending a special flag in initialize message) b) trezor receives entropy B from external source c) trezor creates sha256(A + B) and uses that as a seed d) trezor prints used seed on a display (probably in BIP39 format) e) user can check on a trusted computer that everything was ok (note that steps b-d are the same regardless of whether the special flag was set) -- Best Regards / S pozdravom, Pavol Rusnak