From: Mike Hearn <mike@plan99•net>
To: Blibbet <blibbet@gmail•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>,
grarpamp <grarpamp@gmail•com>,
bitcoin-list@lists•sourceforge.net
Subject: Re: [Bitcoin-development] [bitcoin-list] BitMail - p2p Email 0.1. beta
Date: Wed, 31 Jul 2013 11:08:53 +0200 [thread overview]
Message-ID: <CANEZrP3E1g7btsjWsjD6twU+3pmGG-2Cfw_kExUGVb9JiYY4iQ@mail.gmail.com> (raw)
In-Reply-To: <51F886F6.1090108@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1768 bytes --]
"Support" for a TPM is a rather tricky thing.
By itself the TPM is independent of any CPU. However, it's also not very
useful (though for Pond's use case, it works).
The TPM gets much more useful when it's integrated with features on the
motherboard, BIOS, CPU, northbridge, IOMMU etc. Then you have a full blown
TCG-compliant TC environment, which is useful for many things. Actually it
was never very useful for DRM - that was only one theoretical possibility
that was never implemented and even if it had been, TC is to DRM much as
cryptography is to DRM. So the FUD was just that: fear, uncertainty and
doubt which probably crippled a highly useful cryptographic security tool
for good. One of the more shameful periods of the tech industries history,
if you ask me.
On Wed, Jul 31, 2013 at 5:39 AM, Blibbet <blibbet@gmail•com> wrote:
> On 7/30/13 3:58 PM, grarpamp wrote:
> > [...] And if AMD even has this stuff. [...]
>
> Yes, AMD does have TPM.
>
> Sorry, not sure which models support it.
>
> http://www.amd.com/us/products/embedded/das/Pages/security.aspx
>
>
> http://www.amd.com/us/products/desktop/platforms/Pages/desktop-platforms.aspx
>
>
>
> ------------------------------------------------------------------------------
> 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: 2731 bytes --]
next prev parent reply other threads:[~2013-07-31 9:09 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 ` [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 [this message]
[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=CANEZrP3E1g7btsjWsjD6twU+3pmGG-2Cfw_kExUGVb9JiYY4iQ@mail.gmail.com \
--to=mike@plan99$(echo .)net \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=bitcoin-list@lists$(echo .)sourceforge.net \
--cc=blibbet@gmail$(echo .)com \
--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