From: Mike Hearn <mike@plan99.net>
To: Eugen Leitl <eugen@leitl.org>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] [bitcoin-list] BitMail - p2p Email 0.1. beta
Date: Wed, 31 Jul 2013 17:54:20 +0200 [thread overview]
Message-ID: <CANEZrP2uexbNM9xwNU1RSSgnRSGvUO69tVz0yL8Z5PXLG0HbSg@mail.gmail.com> (raw)
In-Reply-To: <CANEZrP3J1+ATYSRcAcJgGtwcJE+XXKjFrdkP-bYQS7VbxKfV-g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1012 bytes --]
Sorry, I just noticed that this thread was CCd to the announce list not the
development list (why is it open access?)
It's offtopic anyway. Let's continue this discussion in private if anyone
wants to.
On Wed, Jul 31, 2013 at 5:53 PM, Mike Hearn <mike@plan99.net> wrote:
>
> The reason why TPM functionality was so much hated upon is because
>> it was pushed by a software/hardware monopoly, not just for DRM but
>> for locking down the system in general.
>>
>
> Regardless of what some people might have imagined or extrapolated at the
> time, the actual published specifications and technologies were nothing
> like that. There has never been a TC/TPM mode that would have generally
> locked systems down or even been useful for DRM (that'd have required a
> trusted hardware path which was never specced nor implemented).
>
> Locking a system down against tampering or for DRM does not require
> flexible open specifications with multiple competing implementations. It
> requires you to do an Xbox 360.
>
[-- Attachment #2: Type: text/html, Size: 1609 bytes --]
next prev parent reply other threads:[~2013-07-31 15:54 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
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 [this message]
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=CANEZrP2uexbNM9xwNU1RSSgnRSGvUO69tVz0yL8Z5PXLG0HbSg@mail.gmail.com \
--to=mike@plan99.net \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=eugen@leitl.org \
/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