From mboxrd@z Thu Jan  1 00:00:00 1970
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 6326C8B4
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Mon, 22 Jun 2015 01:14:05 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-oi0-f41.google.com (mail-oi0-f41.google.com
	[209.85.218.41])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 0FD2C126
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Mon, 22 Jun 2015 01:14:05 +0000 (UTC)
Received: by oigb199 with SMTP id b199so70240079oig.3
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Sun, 21 Jun 2015 18:14:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:date:message-id:subject:from:to:content-type;
	bh=74v733eGrcom10NwIIOU0qDosPLxNaQOUIoCmUMDZ08=;
	b=k+OE/vyeij8OlcytOZBOzA2nJfiZ/tNN7FTVQrXtpeb8TsyXw6QUl3TTTISwGuS01H
	RUv7lNkRpwPgCHPSdFJSWd5GOK1qnPEmYG2hkrkUMTn8EhP4WlD2uLT/hvYv8xoqN7F/
	cre6S939K+Ll4SBoD/6794ipdQRlzIHwU8RTv9Kg4xnus45Sg2dtFYXYhswsqBAp4kZp
	c+IWH/X/H2wePhxLcnRTeuuo/w/GJmznzgGUy+0vqWmtJC+9k7ThlrRE4hP8xKrjJWVr
	cNHzfZAiedkpkmT3MMpRHEAYvSKx8FOj9OaRFajfApce2cqEATknoCL7DjOdONjd13vP
	/pHg==
MIME-Version: 1.0
X-Received: by 10.202.10.193 with SMTP id 184mr21811208oik.90.1434935644442;
	Sun, 21 Jun 2015 18:14:04 -0700 (PDT)
Received: by 10.60.174.163 with HTTP; Sun, 21 Jun 2015 18:14:04 -0700 (PDT)
Date: Sun, 21 Jun 2015 20:14:04 -0500
Message-ID: <CALxyHsVWsZOxN3Gwh0_AmjE2nCs=w+FS88fDHRQ7dFfkx_HPAw@mail.gmail.com>
From: Frank Flores <frankf44@gmail.com>
To: bitcoin-dev@lists.linuxfoundation.org
Content-Type: multipart/alternative; boundary=001a113d1dc65cd721051910fd64
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
Subject: [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 01:14:05 -0000

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

If you're going to go through the trouble of signing your public emails,
please publish your public key on a major key server or at least somewhere
where google can crawl it. Thank you.

-- 
*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

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

<div dir=3D"ltr">If you&#39;re going to go through the trouble of signing y=
our public emails, please publish your public key on a major key server or =
at least somewhere where google can crawl it. Thank you.<br clear=3D"all"><=
div><br></div>-- <br><div class=3D"gmail_signature"><div style=3D"text-alig=
n:left"><b><span style=3D"font-size:xx-large">MONEY IS OVER!</span></b></di=
v><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.zeitgeistmov=
ie.com/" target=3D"_blank">IF YOU 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>Th=
e causes of my servitude can be traced to the tyranny of money.<br>-Serj Ta=
nkian</div></div>
</div>

--001a113d1dc65cd721051910fd64--


From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <pete@petertodd.org>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
	[172.17.192.35])
	by mail.linuxfoundation.org (Postfix) with ESMTPS id B739CAE7
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Mon, 22 Jun 2015 02:07:02 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from outmail149075.authsmtp.net (outmail149075.authsmtp.net
	[62.13.149.75])
	by smtp1.linuxfoundation.org (Postfix) with ESMTP id CDF037C
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Mon, 22 Jun 2015 02:07:01 +0000 (UTC)
Received: from mail-c237.authsmtp.com (mail-c237.authsmtp.com [62.13.128.237])
	by punt16.authsmtp.com (8.14.2/8.14.2/) with ESMTP id t5M26vWj001610;
	Mon, 22 Jun 2015 03:06:57 +0100 (BST)
Received: from savin.petertodd.org (75-119-251-161.dsl.teksavvy.com
	[75.119.251.161]) (authenticated bits=128)
	by mail.authsmtp.com (8.14.2/8.14.2/) with ESMTP id t5M26qIE061101
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO);
	Mon, 22 Jun 2015 03:06:55 +0100 (BST)
Date: Sun, 21 Jun 2015 22:06:52 -0400
From: Peter Todd <pete@petertodd.org>
To: Frank Flores <frankf44@gmail.com>
Message-ID: <20150622020652.GA21212@savin.petertodd.org>
References: <CALxyHsVWsZOxN3Gwh0_AmjE2nCs=w+FS88fDHRQ7dFfkx_HPAw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
	protocol="application/pgp-signature"; boundary="ew6BAiZeqk4r7MaW"
Content-Disposition: inline
In-Reply-To: <CALxyHsVWsZOxN3Gwh0_AmjE2nCs=w+FS88fDHRQ7dFfkx_HPAw@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-Server-Quench: 5b730d1d-1883-11e5-9f74-002590a135d3
X-AuthReport-Spam: If SPAM / abuse - report it at:
	http://www.authsmtp.com/abuse
X-AuthRoute: OCd2Yg0TA1ZNQRgX IjsJECJaVQIpKltL GxAVKBZePFsRUQkR
	aAdMdAAUEkAaAgsB AmMbW1deUFt7XGY7 bA9PbARUfEhLXhtr
	VklWR1pVCwQmRRl8 BBhfK2xycQRHeH8+ Y09rXT5eDkN5dRJ8
	FlNVHWUFeGZhPWUC WRZfcx5UcAFPdx8U a1N6AHBDAzANdhEy
	HhM4ODE3eDlSNhEd YBwWMRo8cGdj
X-Authentic-SMTP: 61633532353630.1024:706
X-AuthFastPath: 0 (Was 255)
X-AuthSMTP-Origin: 75.119.251.161/587
X-AuthVirus-Status: No virus detected - but ensure you scan with your own
	anti-virus system.
X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,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 02:07:02 -0000


--ew6BAiZeqk4r7MaW
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sun, Jun 21, 2015 at 08:14:04PM -0500, Frank Flores wrote:
> If you're going to go through the trouble of signing your public emails,
> please publish your public key on a major key server or at least somewhere
> where google can crawl it. Thank you.

As for how you can do that, on stock gnupg:

    gpg --send-key 934023AE18144354

Or possibly:

    gpg --keyserver hkp://keys.gnupg.net --send-key 934023AE18144354

If your gpg.conf doesn't have a keyserver set.

Note that if you add a new subkey (as well as other changes to your key)
you need to resend your key to the keyservers or people won't be able to
verify your signatures.


Disclaimer: OpenPGP kinda sucks. Deal with it.

--=20
'peter'[:-1]@petertodd.org
000000000000000006e2d86bc8460d5900351f1cf9b2b4e4acdebc1d0a063901

--ew6BAiZeqk4r7MaW
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature

-----BEGIN PGP SIGNATURE-----

iQGrBAEBCACVBQJVh224XhSAAAAAABUAQGJsb2NraGFzaEBiaXRjb2luLm9yZzAw
MDAwMDAwMDAwMDAwMDAxNWViZjllNGFiYzk3MDY0ODJkZGQwZTc3NGQ1ZGE1NDEz
NDNlOWRlY2Q2MzhlNGMvFIAAAAAAFQARcGthLWFkZHJlc3NAZ251cGcub3JncGV0
ZUBwZXRlcnRvZC5vcmcACgkQJIFAPaXwkftfiQf/arPvuLT/kqcHXy+Ohuoioeia
FQmvw/PKvJ6AlWD7XgyR+Yu4DHAveqoQZ+KWt/N0Fbz/4CWkVAEtKq9YFq+pM2a7
yOk9+ipxKvKbdca8cnghW6EXBx9jusGUTn4EvcF5jgCqVadkKzoZMAWLmSLZMjPv
vavrMKDO2Xm0XEdl/swoDaiEEtzO4WPHY+vJ3GQ4h4QB4daZYGXzdYU7jRFiEHmY
WGodberFwHlPvMnGJ4KU5OvlgoNS4Zy+wrPE2uisyxBkUWHnk6IPoRtP1MwCipmY
FL2SNedDFQaST0It8DPSZnw9rXOHoa9zDzhegKtvyj7YOzxwt3DX5OTKSWpFog==
=5BD6
-----END PGP SIGNATURE-----

--ew6BAiZeqk4r7MaW--


From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <venzen@mail.bihthai.net>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
	[172.17.192.35])
	by mail.linuxfoundation.org (Postfix) with ESMTPS id 63B5B93E
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Mon, 22 Jun 2015 06:49:39 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from mail.bihthai.net (unknown [5.255.87.165])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 912D3141
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Mon, 22 Jun 2015 06:49:38 +0000 (UTC)
Received: from [10.8.0.6] (unknown [10.8.0.6])
	(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
	(No client certificate requested) (Authenticated sender: venzen)
	by mail.bihthai.net (Postfix) with ESMTPSA id CE4371E5D2;
	Mon, 22 Jun 2015 08:50:05 +0200 (CEST)
Message-ID: <5587AFFC.1010307@mail.bihthai.net>
Date: Mon, 22 Jun 2015 13:49:32 +0700
From: Venzen Khaosan <venzen@mail.bihthai.net>
Organization: Bihthai Bai Mai
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
	rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: bitcoin-dev@lists.linuxfoundation.org, peter@petertodd.org
References: <CALxyHsVWsZOxN3Gwh0_AmjE2nCs=w+FS88fDHRQ7dFfkx_HPAw@mail.gmail.com>
	<20150622020652.GA21212@savin.petertodd.org>
In-Reply-To: <20150622020652.GA21212@savin.petertodd.org>
OpenPGP: id=1CF07D66;
	url=pool.sks-keyservers.net
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
X-Spam-Status: No, score=-1.1 required=5.0 tests=BAYES_00,RDNS_NONE
	autolearn=no version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
	smtp1.linux-foundation.org
Subject: Re: [bitcoin-dev] Just FYI
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: venzen@mail.bihthai.net
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 06:49:39 -0000

-----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-----


From mboxrd@z Thu Jan  1 00:00:00 1970
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--