1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <stick@gk2.sk>) id 1WNp5D-0006um-F1
for bitcoin-development@lists.sourceforge.net;
Wed, 12 Mar 2014 19:44:55 +0000
X-ACL-Warn:
Received: from mail-ea0-f171.google.com ([209.85.215.171])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1WNp5B-0005s6-72
for bitcoin-development@lists.sourceforge.net;
Wed, 12 Mar 2014 19:44:55 +0000
Received: by mail-ea0-f171.google.com with SMTP id n15so61492ead.16
for <bitcoin-development@lists.sourceforge.net>;
Wed, 12 Mar 2014 12:44:46 -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
:content-transfer-encoding;
bh=99qCS2jsMRf0QtJWjBgQEA41Kbwmj+2F7DZrxEncU2Y=;
b=UFCc/G+/joOKO+om3ru5V5CYgku3qYdlrHa9ICk16l6PKpvjQ5Ib9I8sjsnfPAPTBV
6t13z+Rwh2t4Dt6DCPmrrWtbhWOFygfXCzuo6ZE4swleNHZld1CbGNkOJhFLQmAkuKcU
1lktoWanFD6BmavsvdpB1KlCqW2Fkl/gjIWlHk8a7CT8zi/XOup7ufveqngsw+e7Ex0+
VTTcT56XcswrPPnl8kPpeDE6DD2VvJhJSTVVEn3ZWE8BR0Yl625nr2Ng+FY/1akgELiv
OVghZScHQ5Actd2suuPnm6OmdZqTxzoyF4sGHKc5klnTX9wCJtSXVHVpNa/lagdPil/b
j42A==
X-Gm-Message-State: ALoCoQlwrZqyKdeHrNyxSNIBKUgxTDRcBaxERJmFpejuiqxgG+bEG5/VShFNnmHDBR4969MQsFrm
X-Received: by 10.15.51.1 with SMTP id m1mr49825056eew.25.1394653172382;
Wed, 12 Mar 2014 12:39:32 -0700 (PDT)
Received: from tetra.site (nat-0-15.lam.cz. [80.92.242.254])
by mx.google.com with ESMTPSA id 43sm73405656eeh.13.2014.03.12.12.39.30
for <multiple recipients>
(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
Wed, 12 Mar 2014 12:39:31 -0700 (PDT)
Message-ID: <5320B7F1.8060701@gk2.sk>
Date: Wed, 12 Mar 2014 20:39:29 +0100
From: Pavol Rusnak <stick@gk2.sk>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Jean-Paul Kogelman <jeanpaulkogelman@me.com>
References: <44fcb02b-3784-45a6-816a-312c78d940cd@me.com>
In-Reply-To: <44fcb02b-3784-45a6-816a-312c78d940cd@me.com>
X-Enigmail-Version: 1.6
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.
X-Headers-End: 1WNp5B-0005s6-72
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] [RFC] Proposal: Base58 encoded HD Wallet
root key with optional encryption
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Wed, 12 Mar 2014 19:44:55 -0000
On 03/12/2014 08:26 PM, Jean-Paul Kogelman wrote:
> So upon entering a password with a typo, the user will not be notified of an
> error, but be presented with a wallet balance of 0, after the blockchain has
> been scanned. I'm sorry, but that's not the kind of experience I would want to
> present to my users.
Sure, you can have either plausible deniability or typo checking, not
both at the same time.
> Would you care to elaborate how optional outsourcing of the KDF breaks
> compatibility?
I'm afraid one would end up with code generated in one client that is
unusable in a different client, because the client's developer thought
that using fancier algorithm instead of the proposed ones was a good idea.
--
Best Regards / S pozdravom,
Pavol Rusnak <stick@gk2.sk>
|
