summaryrefslogtreecommitdiff
path: root/ec/ea3c436c14b9a8c911a9aeccf29d572c96864a
blob: e1a308f6ec131c976cb89527e80f3eb2b63b7da0 (plain)
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
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
Return-Path: <frankf44@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
	[172.17.192.35])
	by mail.linuxfoundation.org (Postfix) with ESMTPS id 9EB09B88
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Mon, 22 Jun 2015 08:45:15 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-ob0-f178.google.com (mail-ob0-f178.google.com
	[209.85.214.178])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id A4F79F2
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Mon, 22 Jun 2015 08:45:14 +0000 (UTC)
Received: by obbop1 with SMTP id op1so15299879obb.2
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Mon, 22 Jun 2015 01:45:14 -0700 (PDT)
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
	:cc:content-type;
	bh=kHo/9HokpfFUDLlxqQQ5Mw8RzXJ5lKiTJAb+RM239GY=;
	b=AjOa6G6cxj1lB+78kspjX0VvmKwCodMgc0LE67nywGj2Oig4X4O0cukcx3q5nTmY8H
	Nd8tPTK99AnmnoaHAy0GP28Jbm/GTXct2ToEYXedulgWnz5bC6jUWUMpWyunFHY582JJ
	rQzc0f1ExMS81i9DLuGPnd1xZ1wHYViwfUx/68eh9IMJQrr8l1vnZIOS8aqJduXI290C
	a6YhO+10aKB/drc9WW3heLubb3eMnpWSYJoyPtWIdJXK4fMUi9aU0/j20+8UUKLRCpYo
	4qw70PytPZIsa9HZdwK0hQb0THnBIEHUzfyDFpd7Gk2CsK8NDb/hyJzSS1VnEx6yAC+1
	x6Hw==
MIME-Version: 1.0
X-Received: by 10.202.194.9 with SMTP id s9mr13020793oif.39.1434962713830;
	Mon, 22 Jun 2015 01:45:13 -0700 (PDT)
Received: by 10.60.174.163 with HTTP; Mon, 22 Jun 2015 01:45:13 -0700 (PDT)
In-Reply-To: <5587AFFC.1010307@mail.bihthai.net>
References: <CALxyHsVWsZOxN3Gwh0_AmjE2nCs=w+FS88fDHRQ7dFfkx_HPAw@mail.gmail.com>
	<20150622020652.GA21212@savin.petertodd.org>
	<5587AFFC.1010307@mail.bihthai.net>
Date: Mon, 22 Jun 2015 03:45:13 -0500
Message-ID: <CALxyHsXWikF9bccqhQiDr=kCfqF2V2X-62raXOJeGMD4dYqyyw@mail.gmail.com>
From: Frank Flores <frankf44@gmail.com>
To: venzen@mail.bihthai.net
Content-Type: multipart/alternative; boundary=001a113dc334d2ebe80519174a52
X-Spam-Status: No, score=-2.4 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	DKIM_VALID,DKIM_VALID_AU,FREEMAIL_ENVFROM_END_DIGIT,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
Cc: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] Just FYI
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 Jun 2015 08:45:15 -0000

--001a113dc334d2ebe80519174a52
Content-Type: text/plain; charset=UTF-8

Whenever a public key is altered in any way it should be
resubmitted/republished, so yes, please do so.

DO NOT PUBLISH YOUR PRIVATE KEY. That is the data used to sign a document.
You only need to publish your PUBLIC KEY or otherwise share it with
recipients of your signed message so that others can verify it as properly
signed or not.

On Mon, Jun 22, 2015 at 1:49 AM, Venzen Khaosan <venzen@mail.bihthai.net>
wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Granted this is not the gnuPG support list, it would help me and most
> members, here, to know just a little more, following your gpg advice
> about publishing keys:
>
> Say, subsequent to publishing a key to a keyserver, I then sign that
> key (or someone else signs it)
>
> 1) would the key need to be published again?
>
> 2) does the key used to sign it need to be published in order to make
> signature verification possible?
>
> Venzen
>
>
> On 06/22/2015 09:06 AM, Peter Todd wrote:
> > gpg --keyserver hkp://keys.gnupg.net --send-key
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1
>
> iQEcBAEBAgAGBQJVh6/4AAoJEGwAhlQc8H1mlL0IAIFZdzyzawOjc43SODLYePo6
> NJU+DRKCQLiNhiED/keCFR/t51XarY4dvgG81wr1qskckRarW6s2ZEWU/2l4oaHa
> Ys+yO5ASbWOp9jbcBWIMFcAou+ULYx732wqEGTXOgSXljrSsuGa4DO+8vSW1UToc
> kY6BhFUa9rjEUQXt+gUqfrXiFlgRFHY4/nd1Tk47VEBipZgcQsJr4j6SYhlXHfbb
> CpixpFeIeVFfdHSNQiDMqPkF3xsTLQcqq2LvZpT8TXrA5vQ0wv/gZH49zIIy5QjR
> xjmSb1tZl0GZRTZ3CYCsoK4Zq4BdhqdU8XIhlwACC2WXHFDnqQrTXwH4nLeWcG0=
> =pYDp
> -----END PGP SIGNATURE-----
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>



-- 
*MONEY IS OVER!*
                                IF YOU WANT IT
<http://www.zeitgeistmovie.com/>
=====================================================
The causes of my servitude can be traced to the tyranny of money.
-Serj Tankian

--001a113dc334d2ebe80519174a52
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Whenever a public key is altered in any way it should be r=
esubmitted/republished, so yes, please do so.<div><br></div><div>DO NOT PUB=
LISH YOUR PRIVATE KEY. That is the data used to sign a document. You only n=
eed to publish your PUBLIC KEY or otherwise share it with recipients of you=
r signed message so that others can verify it as properly signed or not.</d=
iv></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Mon, =
Jun 22, 2015 at 1:49 AM, Venzen Khaosan <span dir=3D"ltr">&lt;<a href=3D"ma=
ilto:venzen@mail.bihthai.net" target=3D"_blank">venzen@mail.bihthai.net</a>=
&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0=
 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">-----BEGIN PGP SIGNED =
MESSAGE-----<br>
Hash: SHA1<br>
<br>
Granted this is not the gnuPG support list, it would help me and most<br>
members, here, to know just a little more, following your gpg advice<br>
about publishing keys:<br>
<br>
Say, subsequent to publishing a key to a keyserver, I then sign that<br>
key (or someone else signs it)<br>
<br>
1) would the key need to be published again?<br>
<br>
2) does the key used to sign it need to be published in order to make<br>
signature verification possible?<br>
<br>
Venzen<br>
<span class=3D""><br>
<br>
On 06/22/2015 09:06 AM, Peter Todd wrote:<br>
&gt; gpg --keyserver hkp://<a href=3D"http://keys.gnupg.net" rel=3D"norefer=
rer" target=3D"_blank">keys.gnupg.net</a> --send-key<br>
</span>-----BEGIN PGP SIGNATURE-----<br>
Version: GnuPG v1<br>
<br>
iQEcBAEBAgAGBQJVh6/4AAoJEGwAhlQc8H1mlL0IAIFZdzyzawOjc43SODLYePo6<br>
NJU+DRKCQLiNhiED/keCFR/t51XarY4dvgG81wr1qskckRarW6s2ZEWU/2l4oaHa<br>
Ys+yO5ASbWOp9jbcBWIMFcAou+ULYx732wqEGTXOgSXljrSsuGa4DO+8vSW1UToc<br>
kY6BhFUa9rjEUQXt+gUqfrXiFlgRFHY4/nd1Tk47VEBipZgcQsJr4j6SYhlXHfbb<br>
CpixpFeIeVFfdHSNQiDMqPkF3xsTLQcqq2LvZpT8TXrA5vQ0wv/gZH49zIIy5QjR<br>
xjmSb1tZl0GZRTZ3CYCsoK4Zq4BdhqdU8XIhlwACC2WXHFDnqQrTXwH4nLeWcG0=3D<br>
=3DpYDp<br>
-----END PGP SIGNATURE-----<br>
_______________________________________________<br>
bitcoin-dev mailing list<br>
<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-dev@lists.=
linuxfoundation.org</a><br>
<a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" =
rel=3D"noreferrer" target=3D"_blank">https://lists.linuxfoundation.org/mail=
man/listinfo/bitcoin-dev</a><br>
</blockquote></div><br><br clear=3D"all"><div><br></div>-- <br><div class=
=3D"gmail_signature"><div style=3D"text-align:left"><b><span style=3D"font-=
size:xx-large">MONEY IS OVER!</span></b></div><div><div style=3D"text-align=
:left"><span style=3D"font-size:x-small">=C2=A0=C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0<a href=3D"http://www.zeitgeistmovie.com/" target=3D"_blank">IF Y=
OU WANT IT</a></span></div>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>The causes of my servitude can be t=
raced to the tyranny of money.<br>-Serj Tankian</div></div>
</div>

--001a113dc334d2ebe80519174a52--