From: Mike Hearn <mike@plan99•net>
To: Andy Parkins <andyparkins@gmail•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] bitcoinj 0.8
Date: Wed, 10 Apr 2013 12:02:09 +0200 [thread overview]
Message-ID: <CANEZrP226ADAaAr5qTdOoTNcBzfDF6pipGDXSNEGqq_kXsVa5w@mail.gmail.com> (raw)
In-Reply-To: <201304100958.51054.andyparkins@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1331 bytes --]
The key in the message was used in my last announcement, so that
establishes continuity there.
But regardless, all mails I send are signed automatically by Gmail using
either the gmail.com consumer key (for my posts to this list) or the
google.com corporate key (for my posts to the bitcoinj lists), see
dkim.orgfor more details on this. Whilst this is not signing in the
GPG web of
trust sense, realistically the Gmail DKIM keys are much safer than any key
I could create/maintain, and my ability to sign mail as hearn@google•com is
controlled by hardware second factors and various other rather intense
security systems I can't discuss.
I've considered just not having the additional Bitcoin-key based signatures
at all, but it would help keep continuity in the case that I leave Google
or if there's a DKIM key rotation.
On Wed, Apr 10, 2013 at 10:58 AM, Andy Parkins <andyparkins@gmail•com>wrote:
> On Tuesday 09 April 2013 22:03:35 Mike Hearn wrote:
>
> > To get bitcoinj 0.8, check out our source from git and then run *git
> fetch
> > --all; git checkout **cbbb1a2bf4d1*. This will place you on the 0.8
> release
> > in a secure manner. This message was written on Tuesday 9th April 2013
> and
>
> Not quite secure yet, because you didn't sign your email.
>
>
> Andy
>
> --
> Dr Andy Parkins
> andyparkins@gmail•com
>
[-- Attachment #2: Type: text/html, Size: 2066 bytes --]
prev parent reply other threads:[~2013-04-10 10:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-09 21:03 Mike Hearn
2013-04-10 8:58 ` Andy Parkins
2013-04-10 10:02 ` Mike Hearn [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=CANEZrP226ADAaAr5qTdOoTNcBzfDF6pipGDXSNEGqq_kXsVa5w@mail.gmail.com \
--to=mike@plan99$(echo .)net \
--cc=andyparkins@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.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