From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 9EB09B88 for ; 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 ; Mon, 22 Jun 2015 08:45:14 +0000 (UTC) Received: by obbop1 with SMTP id op1so15299879obb.2 for ; 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: <20150622020652.GA21212@savin.petertodd.org> <5587AFFC.1010307@mail.bihthai.net> Date: Mon, 22 Jun 2015 03:45:13 -0500 Message-ID: From: Frank Flores 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 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 --001a113dc334d2ebe80519174a52 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Whenever a public key is altered in any way it should be r= esubmitted/republished, so yes, please do so.

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.

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=3D
=3DpYDp
-----END PGP SIGNATURE-----
_______________________________________________
bitcoin-dev mailing list
bitcoin-dev@lists.= linuxfoundation.org
https://lists.linuxfoundation.org/mail= man/listinfo/bitcoin-dev



--
MONEY IS OVER!
=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=A0IF Y= OU WANT IT
=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
The causes of my servitude can be t= raced to the tyranny of money.
-Serj Tankian
--001a113dc334d2ebe80519174a52--