Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 63B5B93E for ; Mon, 22 Jun 2015 06:49:39 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from mail.bihthai.net (unknown [5.255.87.165]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 912D3141 for ; Mon, 22 Jun 2015 06:49:38 +0000 (UTC) Received: from [10.8.0.6] (unknown [10.8.0.6]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: venzen) by mail.bihthai.net (Postfix) with ESMTPSA id CE4371E5D2; Mon, 22 Jun 2015 08:50:05 +0200 (CEST) Message-ID: <5587AFFC.1010307@mail.bihthai.net> Date: Mon, 22 Jun 2015 13:49:32 +0700 From: Venzen Khaosan Organization: Bihthai Bai Mai User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0 MIME-Version: 1.0 To: bitcoin-dev@lists.linuxfoundation.org, peter@petertodd.org References: <20150622020652.GA21212@savin.petertodd.org> In-Reply-To: <20150622020652.GA21212@savin.petertodd.org> OpenPGP: id=1CF07D66; url=pool.sks-keyservers.net Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.1 required=5.0 tests=BAYES_00,RDNS_NONE autolearn=no version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.linux-foundation.org Subject: Re: [bitcoin-dev] Just FYI X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: venzen@mail.bihthai.net List-Id: Bitcoin Development Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Jun 2015 06:49:39 -0000 -----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-----