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
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
|
Return-Path: <adam.back@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 3708AFE1
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 23 Jan 2018 14:16:25 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-qt0-f179.google.com (mail-qt0-f179.google.com
[209.85.216.179])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 31D8C2C4
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 23 Jan 2018 14:16:24 +0000 (UTC)
Received: by mail-qt0-f179.google.com with SMTP id o35so1532054qtj.13
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 23 Jan 2018 06:16:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
h=mime-version:reply-to:in-reply-to:references:from:date:message-id
:subject:to:cc:content-transfer-encoding;
bh=/lbkOYc6mnrhvl6tUu2j5rKIjSWnBaCHabm9Eiws/oU=;
b=bjrVGsRmrXxmv8QnumDoka78LQA0MtKamrD+lE4nks07fismHNokbimtm+tcVDd4jz
m5JvLJtZpqU2iskBObtXlpcs+91SuONM0PrHjVFDTlUGEsCVI/Hqjcm7Trbq5FzG7R7R
OVQdzXv+/mApWmB+j/8PGJTWL87jLEPe0BuX8Kqg0a8D1wgClxw2GtwNGLK0ef+dh/ZQ
8N5CZyFWmeUXImUSvZJv46LpYEz4Z6Cpl1mkraWozre8pkYbPVMOwX4g5PFw5T70iVjN
LkCWxCPWKqfITLQiSdT0rC1lLCz5CG9zTdtRF2iNBa5v33HlNMnlXCjfEhp/4gyJNESh
MWdA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20161025;
h=x-gm-message-state:mime-version:reply-to:in-reply-to:references
:from:date:message-id:subject:to:cc:content-transfer-encoding;
bh=/lbkOYc6mnrhvl6tUu2j5rKIjSWnBaCHabm9Eiws/oU=;
b=eMDIZ9AArWqt1ToeBr9pagkkirR9c3VAb+sKYdzu0r6nLGQ6g3laWxsqI9YPgEdhfP
9hQXfwg4kfphCOpp7ZY6snM5i1riwF8cb2ev1EYgx54e3/+UcCAR1fmBJFS70t1xnsZY
pE3fLT0ToDfmCt54RrMLmiI5RFVAs1PsmUvZZIbZaHk4eVmivpGegWxLssj19dGMMBVH
SkDHfJRFludKAJ0nLO30VX1zQmnlT/vQ5GezH9n/E/UURV8VggY2FAPs9cXffl0fkd3d
4OYLmHbsNqTOg8k7m56XEYhpX3ct5da7UydLAK5en6ClepjphHmud2dzGn0A+8YghS8u
rPBw==
X-Gm-Message-State: AKwxytdFrynj/Aw7SHanlowzZDZI7eGBwFlmygpZYvJSIBK4PKZzQaj5
3DY5kQwGsiVGIw3q/kTpTXbkTDiKLKJlGr0qxHI=
X-Google-Smtp-Source: AH8x226vnrEfGIHDpPegEMH5zgz9SbOVPO7rNNRvTCvpFSnC69oWJkkJsR77xPXDSWle5TrO++84xqFiP8SVB3FB144=
X-Received: by 10.55.153.135 with SMTP id b129mr3436096qke.205.1516716983251;
Tue, 23 Jan 2018 06:16:23 -0800 (PST)
MIME-Version: 1.0
Received: by 10.12.136.207 with HTTP; Tue, 23 Jan 2018 06:16:22 -0800 (PST)
Reply-To: adam@cypherspace.org
In-Reply-To: <bf402c77-cfdd-f38d-43a9-23f1c3273b9d@satoshilabs.com>
References: <51280a45-f86b-3191-d55e-f34e880c1da8@satoshilabs.com>
<CAAS2fgRQk4EUp6FO2f+RkJpDTyZX0N4=uGp7ZF=0aUchZX8hSA@mail.gmail.com>
<4003eed1-584f-9773-8cf9-6300ebd1eac6@satoshilabs.com>
<CAAS2fgSw0mAQPJ-ai-3kFr7pWXd7pjbrEoXN4r6Ak3o4c8_vjw@mail.gmail.com>
<d6eb0fc3-d729-30cb-986b-b1d7b8aacbd6@satoshilabs.com>
<CAAS2fgQtf_LDDcWDmvM+kjPCSqaQVwVd2rKWVtho4-XSAHpJZQ@mail.gmail.com>
<bf402c77-cfdd-f38d-43a9-23f1c3273b9d@satoshilabs.com>
From: Adam Back <adam.back@gmail.com>
Date: Tue, 23 Jan 2018 06:16:22 -0800
Message-ID: <CALqxMTGq6Z6sh0oTuJrU=toCj0c+WJbSQQxhJkNtZuthRUtPog@mail.gmail.com>
To: =?UTF-8?Q?Ond=C5=99ej_Vejpustek?= <ondrej.vejpustek@satoshilabs.com>,
Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM,
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
Subject: Re: [bitcoin-dev] Satoshilabs secret shared private key scheme
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Protocol Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Jan 2018 14:16:25 -0000
Makwa sites [1] https://bitcointalk.org/index.php?topic=3D311000.0
Seems like they independently rediscovered it.
Adam
On 23 January 2018 at 05:54, Ond=C5=99ej Vejpustek via bitcoin-dev
<bitcoin-dev@lists.linuxfoundation.org> wrote:
>> Yes, this scheme.
>> https://bitcointalk.org/index.php?topic=3D311000.msg3342217#msg3342217
>
> In addition to the scheme, I found out, that Makwa
> (https://www.bolet.org/makwa/), a hashing function which received a
> special recognition in the Password Hashing Competition, supports a
> delegation. In fact, Makwa is similar to the suggested scheme.
>
> Unfortunately, both schemes have two drawbacks:
> (1) There is no proof that the host computes what he's suppose to do.
> (2) The delegation is far more slower than the normal computation.
> According to the Makwa paper
> (https://www.bolet.org/makwa/makwa-spec-20150422.pdf) the delegation is
> typically 100 to 1000 slower. So I see little advantage in delegating.
>
> I doubt there is a scheme that suits our needs.
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
|
