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
|
Return-Path: <eth3rs@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id E383BA5D
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 22 Feb 2016 18:06:57 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-vk0-f42.google.com (mail-vk0-f42.google.com
[209.85.213.42])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 4FD97181
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 22 Feb 2016 18:06:57 +0000 (UTC)
Received: by mail-vk0-f42.google.com with SMTP id c3so137371968vkb.3
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 22 Feb 2016 10:06:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
h=mime-version:in-reply-to:references:date:message-id:subject:from:to
:content-type; bh=0OGjuuyNGngx9Lvl84zSywL7FrmrzoT+MFv/rCWxZGo=;
b=qH6uY1bQ8g/qHsEYniSDNafy7T4i1uLKrZ3bBiEYJ43v5HN658BUArPNgKuBZTXCOQ
dFa1z1YgoMJm4jWpziZuooTyvdM0V/JufCbD1ML4aAhvEHf8fyUADLMj6Kk/LIK8+g8F
5oc5TtIACRMWlFRfxAF3g1kUKSrj2/bm06L4Vc9Os76ptguYCeAlIXc1v4jd1jGZ77jK
z54RbzYSLMkxlzpKHIP9e7kxM0KS5K9DN5WjIPGeJNSO/ShKm3koAuAQ4t/rETFMKuN5
TFCKDuqDcW30ZqycR/Q5F2rW8CgidsVYCTyy7OxkBz0KSfzdWVKXBhK6jo+i3m/76sNE
ZSWQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:mime-version:in-reply-to:references:date
:message-id:subject:from:to:content-type;
bh=0OGjuuyNGngx9Lvl84zSywL7FrmrzoT+MFv/rCWxZGo=;
b=c8wlSl57PY8PHVg9fBqgOAXgGUSveOkOgCInIF51PhP/7v/eIgeodRgtwSCeOocmmq
eBIK+o+pbaRLYzELWm86dYo2Drrn97GC2XZBZghRh++BHYOXa6mqoRqvoR+vYgKyTji7
nTKalVM9M1E4dH0jquns5zx30E8tL1tpXlV6hAfN4RSbdapYkJQDGvbubuDGhhWSQdKC
0GgH+h7uG5uYOwO8PbjGSgpv5Dktewq+WuEw0yumBl4LeTmpgAK2eVz1V5U5HeGUoEDh
Q2r6BaebdlpMCcFxY5b2ls0ynzv65W7EnSSf1oDJhRs9IKFeFbg0jjUJfqZVSg+DViE2
UhZQ==
X-Gm-Message-State: AG10YOTctCcS+2hxgWE8F+QIU97X90sjwsJrgMsP+K40FxxkblUH4zxpwFAzCQk2bHRIWyGXccJOuV06UJ4h/A==
MIME-Version: 1.0
X-Received: by 10.31.194.130 with SMTP id s124mr23904380vkf.92.1456164416326;
Mon, 22 Feb 2016 10:06:56 -0800 (PST)
Received: by 10.176.4.118 with HTTP; Mon, 22 Feb 2016 10:06:56 -0800 (PST)
Received: by 10.176.4.118 with HTTP; Mon, 22 Feb 2016 10:06:56 -0800 (PST)
In-Reply-To: <CAEM=y+W0XkWEPcKwBsyHSp8OSVyZ0B0YN65v11No5kK05fE1wg@mail.gmail.com>
References: <CAEM=y+W0XkWEPcKwBsyHSp8OSVyZ0B0YN65v11No5kK05fE1wg@mail.gmail.com>
Date: Mon, 22 Feb 2016 13:06:56 -0500
Message-ID: <CAEM=y+WhxR-GNY_O1pvY0F_DjB1XSpDRR28q38HhscUES9tR3g@mail.gmail.com>
From: Ethan Heilman <eth3rs@gmail.com>
To: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary=001a11378f44c5150e052c5fb2b7
X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,HTML_MESSAGE,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
X-Mailman-Approved-At: Mon, 22 Feb 2016 18:19:55 +0000
Subject: [bitcoin-dev] New paper: On Bitcoin Security in the Presence of
Broken Crypto Primitives
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: Mon, 22 Feb 2016 18:06:58 -0000
--001a11378f44c5150e052c5fb2b7
Content-Type: text/plain; charset=UTF-8
"*Abstract: *Digital currencies like Bitcoin rely on cryptographic
primitives to operate. However, past experience shows that cryptographic
primitives do not last forever: increased computational power and advanced
cryptanalysis cause primitives to break frequently, and motivate the
development of new ones. It is therefore crucial for maintaining trust in a
crypto currency to anticipate such breakage.
We present the first systematic analysis of the effect of broken primitives
on Bitcoin. We identify the core cryptographic building blocks and analyze
the various ways in which they can break, and the subsequent effect on the
main Bitcoin security guarantees. Our analysis reveals a wide range of
possible effects depending on the primitive and type of breakage, ranging
from minor privacy violations to a complete breakdown of the currency.
Our results lead to several observations on, and suggestions for, the
Bitcoin migration plans in case of broken cryptographic primitives."
https://eprint.iacr.org/2016/167
--001a11378f44c5150e052c5fb2b7
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<p dir=3D"ltr">"<b>Abstract:=C2=A0</b>Digital currencies like Bitcoin =
rely on cryptographic primitives to operate. However, past experience shows=
that cryptographic primitives do not last forever: increased computational=
power and advanced cryptanalysis cause primitives to break frequently, and=
motivate the development of new ones. It is therefore crucial for maintain=
ing trust in a crypto currency to anticipate such breakage.<br>
We present the first systematic analysis of the effect of broken primitives=
on Bitcoin. We identify the core cryptographic building blocks and analyze=
the various ways in which they can break, and the subsequent effect on the=
main Bitcoin security guarantees. Our analysis reveals a wide range of pos=
sible effects depending on the primitive and type of breakage, ranging from=
minor privacy violations to a complete breakdown of the currency.<br>
Our results lead to several observations on, and suggestions for, the Bitco=
in migration plans in case of broken cryptographic primitives."</p>
<p dir=3D"ltr"><a href=3D"https://eprint.iacr.org/2016/167">https://eprint.=
iacr.org/2016/167</a></p>
--001a11378f44c5150e052c5fb2b7--
|
