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
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <laanwj@gmail.com>) id 1SgHDC-0007sz-8a
for bitcoin-development@lists.sourceforge.net;
Sun, 17 Jun 2012 15:16:22 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.160.47 as permitted sender)
client-ip=209.85.160.47; envelope-from=laanwj@gmail.com;
helo=mail-pb0-f47.google.com;
Received: from mail-pb0-f47.google.com ([209.85.160.47])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-MD5:128)
(Exim 4.76) id 1SgHDA-0007on-0v
for bitcoin-development@lists.sourceforge.net;
Sun, 17 Jun 2012 15:16:22 +0000
Received: by pbbrq2 with SMTP id rq2so6697318pbb.34
for <bitcoin-development@lists.sourceforge.net>;
Sun, 17 Jun 2012 08:16:14 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.68.230.68 with SMTP id sw4mr41871136pbc.142.1339946174009;
Sun, 17 Jun 2012 08:16:14 -0700 (PDT)
Received: by 10.143.44.2 with HTTP; Sun, 17 Jun 2012 08:16:13 -0700 (PDT)
In-Reply-To: <20120617120447.GA26357@vps7135.xlshosting.net>
References: <20120616192651.GA13438@vps7135.xlshosting.net>
<CANEZrP0hGk63_9z3VLGGGw=VUZKC8tNorJF+2udmjZgCfDK-Tw@mail.gmail.com>
<20120617120447.GA26357@vps7135.xlshosting.net>
Date: Sun, 17 Jun 2012 17:16:13 +0200
Message-ID: <CA+s+GJAc8ZX9ziapULE7KJpJUonTv+sfncw0RGLwu_YPQrM=zw@mail.gmail.com>
From: Wladimir <laanwj@gmail.com>
To: Pieter Wuille <pieter.wuille@gmail.com>
Content-Type: multipart/alternative; boundary=047d7b339e6fb8529c04c2ac870f
X-Spam-Score: -0.6 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(laanwj[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
author's domain
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1SgHDA-0007on-0v
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] After compressed pubkeys: hybrid pubkeys
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: Sun, 17 Jun 2012 15:16:22 -0000
--047d7b339e6fb8529c04c2ac870f
Content-Type: text/plain; charset=UTF-8
On Sun, Jun 17, 2012 at 2:04 PM, Pieter Wuille <pieter.wuille@gmail.com>wrote:
> On Sun, Jun 17, 2012 at 01:01:12PM +0200, Mike Hearn wrote:
> > > * 0x04 [32-byte X coord] [32-byte Y coord]: uncompressed format
> > > * 0x06 [32-byte X coord] [32-byte Y coord]: hybrid format for even Y
> coords
> > > * 0x07 [32-byte X coord] [32-byte Y coord]: hybrid format for odd Y
> coords
> >
> > So what's the actual difference in format? Is there any at all, or
> > it's just the first number that's different?
>
> >From what I understand, that is indeed the only difference.
>
>
To prevent surprises in the future, in case OpenSSL decides to add more,
can we disable all other key formats in advance?
Wladimir
--047d7b339e6fb8529c04c2ac870f
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<br><div class=3D"gmail_quote">On Sun, Jun 17, 2012 at 2:04 PM, Pieter Wuil=
le <span dir=3D"ltr"><<a href=3D"mailto:pieter.wuille@gmail.com" target=
=3D"_blank">pieter.wuille@gmail.com</a>></span> wrote:<br><blockquote cl=
ass=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;p=
adding-left:1ex">
<div class=3D"im">On Sun, Jun 17, 2012 at 01:01:12PM +0200, Mike Hearn wrot=
e:<br>
> > * 0x04 [32-byte X coord] [32-byte Y coord]: uncompressed format<b=
r>
> > * 0x06 [32-byte X coord] [32-byte Y coord]: hybrid format for eve=
n Y coords<br>
> > * 0x07 [32-byte X coord] [32-byte Y coord]: hybrid format for odd=
Y coords<br>
><br>
> So what's the actual difference in format? Is there any at all, or=
<br>
> it's just the first number that's different?<br>
<br>
</div>>From what I understand, that is indeed the only difference.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br></font></span></blockquo=
te><div><br>
To prevent surprises in the future, in case OpenSSL decides to add more, ca=
n we disable all other key formats in advance?<br><br>
Wladimir <br><br></div></div>
--047d7b339e6fb8529c04c2ac870f--
|
