MIME-Version: 1.0
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
Cc: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] Just FYI
Precedence: list

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