1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <pete@petertodd.org>) id 1YcE5B-0004Ys-Eo
for bitcoin-development@lists.sourceforge.net;
Sun, 29 Mar 2015 14:20:57 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of petertodd.org
designates 62.13.148.154 as permitted sender)
client-ip=62.13.148.154; envelope-from=pete@petertodd.org;
helo=outmail148154.authsmtp.co.uk;
Received: from outmail148154.authsmtp.co.uk ([62.13.148.154])
by sog-mx-2.v43.ch3.sourceforge.com with esmtp (Exim 4.76)
id 1YcE59-0005dl-SK for bitcoin-development@lists.sourceforge.net;
Sun, 29 Mar 2015 14:20:57 +0000
Received: from mail-c237.authsmtp.com (mail-c237.authsmtp.com [62.13.128.237])
by punt15.authsmtp.com (8.14.2/8.14.2/) with ESMTP id t2TEKm7R021782;
Sun, 29 Mar 2015 15:20:48 +0100 (BST)
Received: from muck (216-15-126-84.c3-0.sbo-ubr1.sbo.ma.cable.rcn.com
[216.15.126.84]) (authenticated bits=128)
by mail.authsmtp.com (8.14.2/8.14.2/) with ESMTP id t2TEKhP5041103
(version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO);
Sun, 29 Mar 2015 15:20:46 +0100 (BST)
Date: Sun, 29 Mar 2015 07:20:43 -0700
From: Peter Todd <pete@petertodd.org>
To: Brian Deery <brian@factom.org>
Message-ID: <20150329142043.GA7204@muck>
References: <CAFjbNjH01=TK1Xfy3W3FG6FO6yqBskPTeyBiVA5FMyR-auEtiQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
protocol="application/pgp-signature"; boundary="xHFwDpU9dbj6ez1V"
Content-Disposition: inline
In-Reply-To: <CAFjbNjH01=TK1Xfy3W3FG6FO6yqBskPTeyBiVA5FMyR-auEtiQ@mail.gmail.com>
X-Server-Quench: caa46290-d61e-11e4-9f74-002590a135d3
X-AuthReport-Spam: If SPAM / abuse - report it at:
http://www.authsmtp.com/abuse
X-AuthRoute: OCd2Yg0TA1ZNQRgX IjsJECJaVQIpKltL GxAVKBZePFsRUQkR
aAdMdAsUFVQGAgsB AmMbWlFeUl17XWU7 aQtXcwRYfEtMWRti
VFdMSlVNFUssA3h0 fUZ+Vxl2dgRGezB3 Y0dmECMKDUB8d099
XxpSFDgbZGY1bH0W BkdcagNUcgZDfk5E aVUrVz1vNG8XDQg5
AwQ0PjZ0MThBJSBS WgQAK04nCWMaViI8 QA0NHSk0VUoDDzkz
IlQ4K1cWHUIQLlR6 NlVpRVIVezEbARFZ GiMFHChaKl9p
X-Authentic-SMTP: 61633532353630.1024:706
X-AuthFastPath: 0 (Was 255)
X-AuthSMTP-Origin: 216.15.126.84/587
X-AuthVirus-Status: No virus detected - but ensure you scan with your own
anti-virus system.
X-Spam-Score: -1.5 (-)
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
X-Headers-End: 1YcE59-0005dl-SK
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] My thoughts on the viability of the
Factom token
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: Sun, 29 Mar 2015 14:20:57 -0000
--xHFwDpU9dbj6ez1V
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Fri, Mar 20, 2015 at 12:46:18AM -0500, Brian Deery wrote:
> Greetings mailing list.
>=20
> Not sure that this content is 100% appropriate here, but Peter Todd
> invited me to post this for archival purposes. The original thread
> has been removed from the search results, but is still up here:
> http://www.reddit.com/r/Bitcoin/comments/2z9k5p/factom_announces_launch_d=
ate_for_software_token/
>=20
>=20
> I have added more thoughts too.
Thanks.
You know, looking though your writeup, I think we're talking past each
other. I've found with a lot of other projects a good way to start is to
explicitly list what you think Factom *prevents* from happening. It is
after all security software - the most important thing it does is what
it prevents the attacker from doing. Be specific - you really need to
nail down exactly what kind of guarantees you're trying to get out of
the Factom system.
--=20
'peter'[:-1]@petertodd.org
0000000000000000064a6b620c22d89697757f4d81c3b839e50b03e2d3f8e168
--xHFwDpU9dbj6ez1V
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
-----BEGIN PGP SIGNATURE-----
iQGrBAEBCACVBQJVGAo4XhSAAAAAABUAQGJsb2NraGFzaEBiaXRjb2luLm9yZzAw
MDAwMDAwMDAwMDAwMDAwNjRhNmI2MjBjMjJkODk2OTc3NTdmNGQ4MWMzYjgzOWU1
MGIwM2UyZDNmOGUxNjgvFIAAAAAAFQARcGthLWFkZHJlc3NAZ251cGcub3JncGV0
ZUBwZXRlcnRvZC5vcmcACgkQwIXyHOf0udyP3gf/SJ48bAQxv08d6PHMVsoiwnLw
v24svd8qMMilUV1mvhj6QNabVChC6nSQTIKr7T1/vQB5TdIp60E6TBmWD3/3beg5
7E7acD8+b/fD+BE76Btv2a/dltuDKO58btHm7PCPSjJ1Yul1B8mq7IGGMk4rI7/B
2P5OGVb83z7MOtY9HJ6FtBfwsq5GrUMXSvauHO16aVWO6KXdZAVsh9Otd3UbE5nO
K8VzW8J5b/kJmjCvk9N6hm9ZMBlbLRCwC9la7COWveyAHkgYhmUyQ4hp1JzoXkkw
bBo/0DHvCjUq11YZZQt5SwWyafBeK5ePbAgpK94AAnu0xuFEi/zuD/GjfPO3Cw==
=DKOZ
-----END PGP SIGNATURE-----
--xHFwDpU9dbj6ez1V--
|
