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
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <mh.in.england@gmail.com>)
id 1V4IEq-0008KO-AR; Tue, 30 Jul 2013 22:17:52 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.219.43 as permitted sender)
client-ip=209.85.219.43; envelope-from=mh.in.england@gmail.com;
helo=mail-oa0-f43.google.com;
Received: from mail-oa0-f43.google.com ([209.85.219.43])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1V4IEo-0008TH-DP; Tue, 30 Jul 2013 22:17:52 +0000
Received: by mail-oa0-f43.google.com with SMTP id i10so12445769oag.30
for <multiple recipients>; Tue, 30 Jul 2013 15:17:45 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.182.56.232 with SMTP id d8mr4574001obq.96.1375222664991;
Tue, 30 Jul 2013 15:17:44 -0700 (PDT)
Sender: mh.in.england@gmail.com
Received: by 10.76.23.36 with HTTP; Tue, 30 Jul 2013 15:17:44 -0700 (PDT)
In-Reply-To: <CAD2Ti29=Lzcun+0Jz7zn2Dt9G2a06f-0V8KEBUMHJTGxhHQV0A@mail.gmail.com>
References: <CAEvNM8=yQn8sE4Lrf5+xedfm4RomBkBVhVWOdFFXxPEk7wZYDw@mail.gmail.com>
<CAAS2fgS=5ju1BFFDkjoRW65qdtojm3rYBHZcSMtUmHhyaTxMhA@mail.gmail.com>
<CANEZrP2+jOTHsEv+qXpqLKJS3UATB_so2ZwQdL+AyJTd2zti4A@mail.gmail.com>
<7B0891A4-7163-43AE-85EC-8BA7ADC28A2A@grabhive.com>
<CANEZrP0OYzz8p6zT_y7JGZyofZ=wTZ=6umCLu0AJy8KH6E0R5A@mail.gmail.com>
<CAD2Ti29=Lzcun+0Jz7zn2Dt9G2a06f-0V8KEBUMHJTGxhHQV0A@mail.gmail.com>
Date: Wed, 31 Jul 2013 00:17:44 +0200
X-Google-Sender-Auth: 0Ud0EAQEJVGGSqKWrFBix009Kbc
Message-ID: <CANEZrP3JVtzBU9mcWvYNuespTi81kaoVUfKAx6vKBWd-hrCqCg@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: grarpamp <grarpamp@gmail.com>
Content-Type: multipart/alternative; boundary=001a11c2c91c6f19c104e2c1fa5b
X-Spam-Score: -0.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 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(mh.in.england[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
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: 1V4IEo-0008TH-DP
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>,
bitcoin-list@lists.sourceforge.net
Subject: Re: [Bitcoin-development] [bitcoin-list] BitMail - p2p Email 0.1.
beta
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: Tue, 30 Jul 2013 22:17:52 -0000
--001a11c2c91c6f19c104e2c1fa5b
Content-Type: text/plain; charset=UTF-8
TPMs have come as standard with nearly all computers (except Macs, doh) for
a long time. They certainly don't cost $100. More like a few dollars at
most. That's why they're so slow.
On Tue, Jul 30, 2013 at 10:43 PM, grarpamp <grarpamp@gmail.com> wrote:
> On Tue, Jul 30, 2013 at 8:12 AM, Mike Hearn <mike@plan99.net> wrote:
> > The TPM is a piece of secure* hardware
>
> I've seen some motherboards with a TPM module header but none
> came with it installed. I think the modules themselves might be
> $50-$100 range. They might come with some API docs.
> Some of you might have links to ones you've used...
>
> > As part of that role, the TPM provides some permanent storage in the form
> > of NVRAM. Because the TPM is designed to be as cheap as possible, it has
> a
> > limited number of write cycles. Normally you're meant to store Intel TXT
> > launch control policies and sealed keys there
>
> > the goal is to avoid wearing down the drive and extend its useful life.
> > Normally it doesn't matter, but if you want to delete data such that it's
> > really really gone, it obviously poses a problem. Using TPM NVRAM solves
> > it, albiet, at a high usability cost.
>
> If said TPM storage has a 'limited [but unfixed number of write cycles',
> that
> sounds unreliable. It would seem to me that both reliable and 'really gone'
> are achievable on platters (or lesser, with ssd) provided the disk was also
> encrypted. Nuke that key and it's reliably gone.
>
>
> ------------------------------------------------------------------------------
> Get your SQL database under version control now!
> Version control is standard for application code, but databases havent
> caught up. So what steps can you take to put your SQL databases under
> version control? Why should you start doing it? Read more to find out.
> http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
> _______________________________________________
> bitcoin-list mailing list
> bitcoin-list@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-list
>
--001a11c2c91c6f19c104e2c1fa5b
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">TPMs have come as standard with nearly all computers (exce=
pt Macs, doh) for a long time. They certainly don't cost $100. More lik=
e a few dollars at most. That's why they're so slow.</div><div clas=
s=3D"gmail_extra">
<br><br><div class=3D"gmail_quote">On Tue, Jul 30, 2013 at 10:43 PM, grarpa=
mp <span dir=3D"ltr"><<a href=3D"mailto:grarpamp@gmail.com" target=3D"_b=
lank">grarpamp@gmail.com</a>></span> wrote:<br><blockquote class=3D"gmai=
l_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left=
:1ex">
<div class=3D"im">On Tue, Jul 30, 2013 at 8:12 AM, Mike Hearn <<a href=
=3D"mailto:mike@plan99.net">mike@plan99.net</a>> wrote:<br>
> The TPM is a piece of secure* hardware<br>
<br>
</div>I've seen some motherboards with a TPM module header but none<br>
came with it installed. I think the modules themselves might be<br>
$50-$100 range. They might come with some API docs.<br>
Some of you might have links to ones you've used...<br>
<div class=3D"im"><br>
> As part of that role, the TPM provides some permanent storage in the f=
orm<br>
> of NVRAM. Because the TPM is designed to be as cheap as possible, it h=
as a<br>
> limited number of write cycles. Normally you're meant to store Int=
el TXT<br>
> launch control policies and sealed keys there<br>
<br>
</div><div class=3D"im">> the goal is to avoid wearing down the drive an=
d extend its useful life.<br>
> Normally it doesn't matter, but if you want to delete data such th=
at it's<br>
> really really gone, it obviously poses a problem. Using TPM NVRAM solv=
es<br>
> it, albiet, at a high usability cost.<br>
<br>
</div>If said TPM storage has a 'limited [but unfixed number of write c=
ycles', that<br>
sounds unreliable. It would seem to me that both reliable and 'really g=
one'<br>
are achievable on platters (or lesser, with ssd) provided the disk was also=
<br>
encrypted. Nuke that key and it's reliably gone.<br>
<div class=3D"im"><br>
---------------------------------------------------------------------------=
---<br>
Get your SQL database under version control now!<br>
Version control is standard for application code, but databases havent<br>
caught up. So what steps can you take to put your SQL databases under<br>
version control? Why should you start doing it? Read more to find out.<br>
<a href=3D"http://pubads.g.doubleclick.net/gampad/clk?id=3D49501711&iu=
=3D/4140/ostg.clktrk" target=3D"_blank">http://pubads.g.doubleclick.net/gam=
pad/clk?id=3D49501711&iu=3D/4140/ostg.clktrk</a><br>
_______________________________________________<br>
</div>bitcoin-list mailing list<br>
<a href=3D"mailto:bitcoin-list@lists.sourceforge.net">bitcoin-list@lists.so=
urceforge.net</a><br>
<a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-list" targe=
t=3D"_blank">https://lists.sourceforge.net/lists/listinfo/bitcoin-list</a><=
br>
</blockquote></div><br></div>
--001a11c2c91c6f19c104e2c1fa5b--
|
