* [bitcoin-dev] Just FYI
@ 2015-06-22 1:14 Frank Flores
2015-06-22 2:06 ` Peter Todd
0 siblings, 1 reply; 4+ messages in thread
From: Frank Flores @ 2015-06-22 1:14 UTC (permalink / raw)
To: bitcoin-dev
[-- Attachment #1: Type: text/plain, Size: 422 bytes --]
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
[-- Attachment #2: Type: text/html, Size: 731 bytes --]
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [bitcoin-dev] Just FYI
2015-06-22 1:14 [bitcoin-dev] Just FYI Frank Flores
@ 2015-06-22 2:06 ` Peter Todd
2015-06-22 6:49 ` Venzen Khaosan
0 siblings, 1 reply; 4+ messages in thread
From: Peter Todd @ 2015-06-22 2:06 UTC (permalink / raw)
To: Frank Flores; +Cc: bitcoin-dev
[-- Attachment #1: Type: text/plain, Size: 810 bytes --]
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.
--
'peter'[:-1]@petertodd.org
000000000000000006e2d86bc8460d5900351f1cf9b2b4e4acdebc1d0a063901
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 650 bytes --]
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [bitcoin-dev] Just FYI
2015-06-22 2:06 ` Peter Todd
@ 2015-06-22 6:49 ` Venzen Khaosan
2015-06-22 8:45 ` Frank Flores
0 siblings, 1 reply; 4+ messages in thread
From: Venzen Khaosan @ 2015-06-22 6:49 UTC (permalink / raw)
To: bitcoin-dev, peter
-----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-----
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [bitcoin-dev] Just FYI
2015-06-22 6:49 ` Venzen Khaosan
@ 2015-06-22 8:45 ` Frank Flores
0 siblings, 0 replies; 4+ messages in thread
From: Frank Flores @ 2015-06-22 8:45 UTC (permalink / raw)
To: venzen; +Cc: bitcoin-dev
[-- 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 --]
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2015-06-22 8:45 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-06-22 1:14 [bitcoin-dev] Just FYI Frank Flores
2015-06-22 2:06 ` Peter Todd
2015-06-22 6:49 ` Venzen Khaosan
2015-06-22 8:45 ` Frank Flores
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox