From: Wendell <w@grabhive.com>
To: Mike Hearn <mike@plan99.net>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>,
bitcoin-list@lists.sourceforge.net
Subject: Re: [Bitcoin-development] BitMail - p2p Email 0.1. beta
Date: Tue, 30 Jul 2013 13:27:02 +0200 [thread overview]
Message-ID: <7B0891A4-7163-43AE-85EC-8BA7ADC28A2A@grabhive.com> (raw)
In-Reply-To: <CANEZrP2+jOTHsEv+qXpqLKJS3UATB_so2ZwQdL+AyJTd2zti4A@mail.gmail.com>
Can you explain this process for those of us not too familiar with TPM chips?
-wendell
grabhive.com | twitter.com/grabhive | gpg: 6C0C9411
On Jul 30, 2013, at 10:40 AM, Mike Hearn wrote:
> As a testament to the seriousness with which Pond takes forward security, it can use the NVRAM in a TPM chip to reliably destroy keys for data that an SSD device might have otherwise made un-erasable.
next prev parent reply other threads:[~2013-07-30 12:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-30 5:01 [Bitcoin-development] BitMail - p2p Email 0.1. beta Randolph D.
2013-07-30 6:50 ` Gregory Maxwell
2013-07-30 8:40 ` Mike Hearn
2013-07-30 11:27 ` Wendell [this message]
2013-07-30 12:12 ` Mike Hearn
[not found] ` <CAD2Ti29=Lzcun+0Jz7zn2Dt9G2a06f-0V8KEBUMHJTGxhHQV0A@mail.gmail.com>
2013-07-30 22:17 ` [Bitcoin-development] [bitcoin-list] " Mike Hearn
[not found] ` <CAD2Ti29zbac5YrW6+oMvb=8t7b1A31XckyC-mH7_qixLCRnFaQ@mail.gmail.com>
[not found] ` <51F886F6.1090108@gmail.com>
2013-07-31 9:08 ` 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=7B0891A4-7163-43AE-85EC-8BA7ADC28A2A@grabhive.com \
--to=w@grabhive.com \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=bitcoin-list@lists.sourceforge.net \
--cc=mike@plan99.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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