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

=====================================================
The causes of my servitude can be traced to the tyranny of money.
-Serj Tankian