From: Peter Pauly <ppauly@gmail.com>
To: Cameron Garnham <da2ce7@gmail.com>
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Signing release binaries
Date: Mon, 30 Jul 2012 09:02:00 -0400 [thread overview]
Message-ID: <CAKXfWbSKV-eNX-0PrLSdRb4bU97zRQtobGRFkeJ6wbA0v7FMdw@mail.gmail.com> (raw)
In-Reply-To: <5015F197.4040302@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 358 bytes --]
I'd like to see the binaries signed with gpg, independent of any signatures
required for various operating systems.
I can't imagine a worse scenario than the bitcoin.org site being hacked and
the binaries replaced with wallet-stealing code. All of the developers seem
to have gpg keys, how hard can it be to provide a detached gpg signature
for the binary?
[-- Attachment #2: Type: text/html, Size: 448 bytes --]
prev parent reply other threads:[~2012-07-30 13:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-29 10:17 [Bitcoin-development] Signing release binaries Mike Hearn
2012-07-29 12:20 ` Peter Vessenes
2012-07-29 17:15 ` Luke-Jr
2012-07-30 2:29 ` Cameron Garnham
2012-07-30 13:02 ` Peter Pauly [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=CAKXfWbSKV-eNX-0PrLSdRb4bU97zRQtobGRFkeJ6wbA0v7FMdw@mail.gmail.com \
--to=ppauly@gmail.com \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=da2ce7@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