Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
	helo=mx.sourceforge.net)
	by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <brianchoffman@gmail.com>) id 1XTWO4-0006Gn-AE
	for bitcoin-development@lists.sourceforge.net;
	Mon, 15 Sep 2014 13:32:12 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.223.176 as permitted sender)
	client-ip=209.85.223.176; envelope-from=brianchoffman@gmail.com;
	helo=mail-ie0-f176.google.com; 
Received: from mail-ie0-f176.google.com ([209.85.223.176])
	by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1XTWO3-0005Wp-3f
	for bitcoin-development@lists.sourceforge.net;
	Mon, 15 Sep 2014 13:32:12 +0000
Received: by mail-ie0-f176.google.com with SMTP id ar1so4348913iec.7
	for <bitcoin-development@lists.sourceforge.net>;
	Mon, 15 Sep 2014 06:32:05 -0700 (PDT)
X-Received: by 10.43.61.129 with SMTP id ww1mr2016592icb.78.1410787925422;
	Mon, 15 Sep 2014 06:32:05 -0700 (PDT)
Received: from [10.173.129.123] ([166.137.83.138])
	by mx.google.com with ESMTPSA id x9sm10087339igl.10.2014.09.15.06.32.04
	for <multiple recipients>
	(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
	Mon, 15 Sep 2014 06:32:04 -0700 (PDT)
Content-Type: text/plain;
	charset=us-ascii
Mime-Version: 1.0 (1.0)
From: Brian Hoffman <brianchoffman@gmail.com>
X-Mailer: iPhone Mail (12A4345d)
In-Reply-To: <CAJHLa0Owjs=6vhy_RSD+VSAZgBq2pSYv5HhCdA4-XCGgX=Z6dA@mail.gmail.com>
Date: Mon, 15 Sep 2014 09:32:03 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <3E354504-0203-4408-85A1-58A071E8546A@gmail.com>
References: <20140913135528.GC6333@muck>
	<CAJHLa0MaE3Ki5Hs4Tu4dQNBW-EL-857N2kf-fVxYcXM6OO-84w@mail.gmail.com>
	<20140914062826.GB21586@muck>
	<201409150923.02817.thomas@thomaszander.se>
	<CAJHLa0Owjs=6vhy_RSD+VSAZgBq2pSYv5HhCdA4-XCGgX=Z6dA@mail.gmail.com>
To: Jeff Garzik <jgarzik@bitpay.com>
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 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
	(brianchoffman[at]gmail.com)
	-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: 1XTWO3-0005Wp-3f
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
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: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Mon, 15 Sep 2014 13:32:12 -0000

I would agree that the in person aspect of the WoT is frustrating, but to di=
smiss this as "geek wanking" is the pot calling the kettle.=20

The value of in person vetting of identity is undeniable. Just because your r=
isk acceptance is difference doesn't make it wanking. Please go see if you c=
an get any kind of governmental clearance of credential without in-person ve=
tting. Ask them if they accept your behavioral signature.=20

I know there is a lot of PGP hating these days but this comment doesn't nece=
ssarily apply to every situation.=20



> On Sep 15, 2014, at 9:08 AM, Jeff Garzik <jgarzik@bitpay.com> wrote:
>=20
>> On Mon, Sep 15, 2014 at 3:23 AM, Thomas Zander <thomas@thomaszander.se> w=
rote:
>> Any and all PGP related howtos will tell you that you should not trust or=
 sign
>> a formerly-untrusted PGP (or GPG for that matter) key without seeing that=

>> person in real life, verifying their identity etc.
>=20
> Such guidelines are a perfect example of why PGP WoT is useless and
> stupid geek wanking.
>=20
> A person's behavioural signature is what is relevant.  We know how
> Satoshi coded and wrote.  It was the online Satoshi with which we
> interacted.  The online Satoshi's PGP signature would be fine...
> assuming he established a pattern of use.
>=20
> As another example, I know the code contributions and PGP key signed
> by the online entity known as "sipa."  At a bitcoin conf I met a
> person with photo id labelled "Pieter Wuille" who claimed to be sipa,
> but that could have been an actor.  Absent a laborious and boring
> signed challenge process, for all we know, "sipa" is a supercomputing
> cluster of 500 gnomes.
>=20
> The point is, the "online entity known as Satoshi" is the relevant
> fingerprint.  That is easily established without any in-person
> meetings.
>=20
> --=20
> Jeff Garzik
> Bitcoin core developer and open source evangelist
> BitPay, Inc.      https://bitpay.com/
>=20
> --------------------------------------------------------------------------=
----
> 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=3D157508191&iu=3D/4140/ostg.=
clktrk
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development