From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1XSnvX-0001Zd-3J for bitcoin-development@lists.sourceforge.net; Sat, 13 Sep 2014 14:03:47 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of bitpay.com designates 209.85.223.176 as permitted sender) client-ip=209.85.223.176; envelope-from=jgarzik@bitpay.com; helo=mail-ie0-f176.google.com; Received: from mail-ie0-f176.google.com ([209.85.223.176]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1XSnvW-0004QH-4c for bitcoin-development@lists.sourceforge.net; Sat, 13 Sep 2014 14:03:47 +0000 Received: by mail-ie0-f176.google.com with SMTP id ar1so2475852iec.21 for ; Sat, 13 Sep 2014 07:03:40 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=P1SrVyXFsF0Z1bLKLO0AyhTREeFXeN8otlXiAhnMyPA=; b=JdeWImFSMxwUygYyv9LXUdkOBSRXahGjS1qc3+vM8rvbRLk0dfEIiPOGnMRlGJNPBi lOiDYawlPXwSLI4DDpcYi3p0CL3L/mjArfImBvsd31UiV8kin82VT303x8Dmgt81bqOb HR6WE5s9n06WGPm9PtSYPGPoGGSYd04p15rRdvSrkW3MuG35+CC/dvbWi3aKNo6HXOF0 iJREfBY5U3koxRw9q/yhbgzicvK0BS9FqBks+wvV3JlCHO+qYqWSpKf44IdZUuUpzN8O eKi7jHQbP2dlKGDRRz0sDwM9nvCUeRCzfp4wHSnarUNaznn82hABRPAo8ApA0GyZLewb 3cWw== X-Gm-Message-State: ALoCoQnYhwluRqksNF7dCkmxC8gKTq0+WUo5/qtpPAGdpGYPxEPcDILblVKwkenkwNX/fBr8Kr4P X-Received: by 10.43.64.77 with SMTP id xh13mr1743124icb.75.1410617020234; Sat, 13 Sep 2014 07:03:40 -0700 (PDT) MIME-Version: 1.0 Received: by 10.107.153.149 with HTTP; Sat, 13 Sep 2014 07:03:20 -0700 (PDT) In-Reply-To: <20140913135528.GC6333@muck> References: <20140913135528.GC6333@muck> From: Jeff Garzik Date: Sat, 13 Sep 2014 10:03:20 -0400 Message-ID: To: Peter Todd Content-Type: text/plain; charset=UTF-8 X-Spam-Score: -1.6 (-) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain -0.0 SPF_PASS SPF: sender matches SPF record -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature X-Headers-End: 1XSnvW-0004QH-4c Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] Does anyone have anything at all signed by Satoshi's PGP key? X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Sep 2014 14:03:47 -0000 That claim is horse manure :) He never signed private emails sent to me, nor the forum posts. He -might- have signed the occasional thing related to releases, I'm not sure. On Sat, Sep 13, 2014 at 9:55 AM, Peter Todd wrote: > So far I have zero evidence that the common claim that "Satoshi PGP > signed everything" was true; I have no evidence he ever > cryptographically signed any communications at all. > > -- > 'peter'[:-1]@petertodd.org > 00000000000000000ce4f740fb700bb8a9ed859ac96ac9871567a20fca07f76a > > ------------------------------------------------------------------------------ > Want excitement? > Manually upgrade your production database. > When you want reliability, choose Perforce > Perforce version control. Predictably reliable. > http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk > _______________________________________________ > Bitcoin-development mailing list > Bitcoin-development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bitcoin-development > -- Jeff Garzik Bitcoin core developer and open source evangelist BitPay, Inc. https://bitpay.com/