From: Mike Hearn <mike@plan99•net>
To: grarpamp <grarpamp@gmail•com>
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
Date: Wed, 31 Jul 2013 00:17:44 +0200 [thread overview]
Message-ID: <CANEZrP3JVtzBU9mcWvYNuespTi81kaoVUfKAx6vKBWd-hrCqCg@mail.gmail.com> (raw)
In-Reply-To: <CAD2Ti29=Lzcun+0Jz7zn2Dt9G2a06f-0V8KEBUMHJTGxhHQV0A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2073 bytes --]
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
>
[-- Attachment #2: Type: text/html, Size: 2937 bytes --]
next prev parent reply other threads:[~2013-07-30 22:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-30 5:01 [Bitcoin-development] " Randolph D.
2013-07-30 6:50 ` Gregory Maxwell
2013-07-30 8:40 ` Mike Hearn
2013-07-30 11:27 ` Wendell
2013-07-30 12:12 ` Mike Hearn
[not found] ` <CAD2Ti29=Lzcun+0Jz7zn2Dt9G2a06f-0V8KEBUMHJTGxhHQV0A@mail.gmail.com>
2013-07-30 22:17 ` Mike Hearn [this message]
[not found] ` <CAD2Ti29zbac5YrW6+oMvb=8t7b1A31XckyC-mH7_qixLCRnFaQ@mail.gmail.com>
[not found] ` <51F886F6.1090108@gmail.com>
2013-07-31 9:08 ` [Bitcoin-development] [bitcoin-list] " Mike Hearn
[not found] ` <20130731133104.GW29404@leitl.org>
[not found] ` <CANEZrP3J1+ATYSRcAcJgGtwcJE+XXKjFrdkP-bYQS7VbxKfV-g@mail.gmail.com>
2013-07-31 15:54 ` Mike Hearn
2013-07-31 16:11 ` [Bitcoin-development] " Randolph D.
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=CANEZrP3JVtzBU9mcWvYNuespTi81kaoVUfKAx6vKBWd-hrCqCg@mail.gmail.com \
--to=mike@plan99$(echo .)net \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=bitcoin-list@lists$(echo .)sourceforge.net \
--cc=grarpamp@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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