public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Peter Todd <pete@petertodd.org>
To: Frank Flores <frankf44@gmail.com>
Cc: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] Just FYI
Date: Sun, 21 Jun 2015 22:06:52 -0400	[thread overview]
Message-ID: <20150622020652.GA21212@savin.petertodd.org> (raw)
In-Reply-To: <CALxyHsVWsZOxN3Gwh0_AmjE2nCs=w+FS88fDHRQ7dFfkx_HPAw@mail.gmail.com>

[-- 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 --]

  reply	other threads:[~2015-06-22  2:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-22  1:14 [bitcoin-dev] Just FYI Frank Flores
2015-06-22  2:06 ` Peter Todd [this message]
2015-06-22  6:49   ` Venzen Khaosan
2015-06-22  8:45     ` Frank Flores

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=20150622020652.GA21212@savin.petertodd.org \
    --to=pete@petertodd.org \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=frankf44@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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