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
109
110
111
112
113
114
115
116
117
118
119
120
121
|
Return-Path: <joroark@vt.edu>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 84040D4A
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 21 Jan 2016 02:57:33 +0000 (UTC)
X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6
Received: from omr1.cc.vt.edu (outbound.smtp.vt.edu [198.82.183.121])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 0198811D
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 21 Jan 2016 02:57:31 +0000 (UTC)
Received: from mr4.cc.vt.edu (mr4.cc.ipv6.vt.edu
[IPv6:2001:468:c80:2105:0:232:8670:19fe])
by omr1.cc.vt.edu (8.14.4/8.14.4) with ESMTP id u0L2vUhP024756
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 20 Jan 2016 21:57:30 -0500
Received: from mail-pf0-f178.google.com (mail-pf0-f178.google.com
[209.85.192.178])
by mr4.cc.vt.edu (8.14.4/8.14.4) with ESMTP id u0L2vPnZ014080
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 20 Jan 2016 21:57:30 -0500
Received: by mail-pf0-f178.google.com with SMTP id e65so15245322pfe.0
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 20 Jan 2016 18:57:30 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:subject:to:references:from:message-id:date
:user-agent:mime-version:in-reply-to:content-type
:content-transfer-encoding;
bh=9v8DWyXm0KmXmKAxHc1h0XxfXjNPP15GW795sCUwD7c=;
b=MeFcSFBQiXjGuTnBEMC4ziBjKWofZjdOxdR+neICcJvlmcrCroIzR8tcsa/MJCsh6L
LcCyuPi+gTNeIydR1mzXynFlY2H3+TAtJz79ykxtNDr/K6nt6rBV3eUMtR92pBiZD0Ss
l17vn8jVuW8qCe45PfJF8QAFw4IXNuZzkmYWeEUwsgfiUYRHqA/rqJxAUC1cHJ+Pqa1K
keNMgOJlJ5ohvNWNM5VeAqVCc19ClAvZV+JmPyuJVH6p9q6yslhzkWnlKrnURuEiWvGZ
LL3UsVOOrh8uqgZcDxMKxVP4a+Lx2xB/RIpOcGTcJtYUp+sAVRnbKEr7J7GS6hw6/cHU
yTpQ==
X-Gm-Message-State: ALoCoQlhJhDRFBkxiQwFDhpsDC5iDiuzucghLi/+4H4h3hA5/F5lfzEGzI730MMqjLEQeO7Ruy7d4e+U3kS2yQUg4RQ/cNc3nPgnc6mojB+bw2bKEYX1iwKVXhVtjs8OU9qGZRV+LaiG63ki31xsyEn/mZ4PHvIA9Sb6p6LySk0ZNl9ooOnG863TaLQ5kms5vOI1pW+BV1MYQdGzIjcf36ITS3czBUb3h2YkWLbiF8nz0ikpPuUH47Q=
X-Received: by 10.98.75.156 with SMTP id d28mr58320835pfj.108.1453345045077;
Wed, 20 Jan 2016 18:57:25 -0800 (PST)
X-Received: by 10.98.75.156 with SMTP id d28mr58320825pfj.108.1453345044933;
Wed, 20 Jan 2016 18:57:24 -0800 (PST)
Received: from [192.168.1.230] (c-24-22-36-12.hsd1.or.comcast.net.
[24.22.36.12]) by smtp.googlemail.com with ESMTPSA id
n5sm51699703pfi.3.2016.01.20.18.57.24
for <bitcoin-dev@lists.linuxfoundation.org>
(version=TLSv1/SSLv3 cipher=OTHER);
Wed, 20 Jan 2016 18:57:24 -0800 (PST)
To: bitcoin-dev@lists.linuxfoundation.org
References: <CADToNK--p5FBxCKXGbab4sa_uOkWL=GxcNKA8f6Dgcz+NE0BMg@mail.gmail.com>
<CAEM=y+XUj00YZ=O98nn_NChBZ0=KiX7nPFegnyrDyOQiPgeGmA@mail.gmail.com>
From: Douglas Roark <joroark@vt.edu>
X-Enigmail-Draft-Status: N1110
Message-ID: <56A04913.90906@vt.edu>
Date: Wed, 20 Jan 2016 18:57:23 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0)
Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <CAEM=y+XUj00YZ=O98nn_NChBZ0=KiX7nPFegnyrDyOQiPgeGmA@mail.gmail.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW,
RP_MATCHES_RCVD 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] What is OpenSSL still used for?
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Development 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: Thu, 21 Jan 2016 02:57:33 -0000
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
On 2016/1/18 19:58, Ethan Heilman via bitcoin-dev wrote:
> I believe libsecp256k1 just performs Elliptic Curve operations
> required by Bitcoin. OpenSSL is used for all other crypto.
The exact answer, as I understand it, is a bit more nuanced. In
particular, you referenced the PRNG. I believe libsecp256k1, as
currently written, relies on an implementation of RFC 6979 instead of
using a PRNG. I'm guessing this is done for portability reasons (no
need to hook into the OS's RNG).
Otherwise, yes, I believe this answer is basically correct. There are
still some crypto functions not covered by libsecp256k1, at least at
the API level. But, for consensus-critical functionality, I think 0.12
will be rid of OpenSSL.
- --
- ---
Douglas Roark
Cryptocurrency, network security, travel, and art.
https://onename.com/droark
joroark@vt.edu
PGP key ID: 26623924
-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org
iQIcBAEBCgAGBQJWoEkTAAoJEEOBHRomYjkkoR0QAKmvgmoOdCw7SLP9cFURltXw
Ro8mOfikjp04C6tsshtiKQ1+jq80wBhioVYIL7XiyNU7ZUNdAWSc/wGBCG+YkMeQ
6h02WJZQtTe0PvGVHIgUw6SiV4ZzXBuapXQX0BgEl0pInvQkRRqWtgrqDlWbqJVg
NKzm8Kh+c8JUHEKbhnC45Jgh2JYHpyXcByLHSyGYsPOprjHmsupCPC6qydrRnuaO
r7YHtObK2myOglJ1h6BXir//+XNbk6RiRNf5voONNAR9L+69BBV7hMVVO3eiDZ12
vrNaOIKhDjhDs1kmkFYi7ML/zKBQRXlb7iM8AEpfCUKl/zK9bSNeblP4ZBGPqjCm
9TGCqGjmKEbg7AYXjyMvmw+jZReediJMNYpCdxaSJi+XJZO6EC28pcKsb6pu/9gX
NCLf1T/f2NoyXxc57aTuHNo0SnVaee1z0+IlGSh+5foxhZGbFmPhxOy3WNIubuou
tm0guAXloCCERwVg0OhhQ3YyrlOWz7VnUrT8cteQC+yP353zdnxay7ZmQh9swcyR
VX7yu4xLcxgbQmBIhMyKs9iQnycOrdNhZEfGx4vQ2ZKAj1CPVqrgKxbtY3KuPfvb
YAzfs/iXaqBHH7FN9juLMRGqkzyVzJ9mIsFyLldADvSoc8RSa1IQiZtfPsIU1w1i
UKEl9Qasje80EojNZNz0
=glL2
-----END PGP SIGNATURE-----
|
