From: Frank Flores <frankf44@gmail•com>
To: venzen@mail•bihthai.net
Cc: bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] Just FYI
Date: Mon, 22 Jun 2015 03:45:13 -0500 [thread overview]
Message-ID: <CALxyHsXWikF9bccqhQiDr=kCfqF2V2X-62raXOJeGMD4dYqyyw@mail.gmail.com> (raw)
In-Reply-To: <5587AFFC.1010307@mail.bihthai.net>
[-- Attachment #1: Type: text/plain, Size: 1932 bytes --]
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
[-- Attachment #2: Type: text/html, Size: 2909 bytes --]
prev parent reply other threads:[~2015-06-22 8:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-22 1:14 Frank Flores
2015-06-22 2:06 ` Peter Todd
2015-06-22 6:49 ` Venzen Khaosan
2015-06-22 8:45 ` Frank Flores [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CALxyHsXWikF9bccqhQiDr=kCfqF2V2X-62raXOJeGMD4dYqyyw@mail.gmail.com' \
--to=frankf44@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=venzen@mail$(echo .)bihthai.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox