From: James Morris <jmorris@namei.org>
To: Mimi Zohar <zohar@linux.ibm.com>
Cc: Lakshmi Ramasubramanian <nramas@linux.microsoft.com>,
linux-integrity@vger.kernel.org,
Matthew Garrett <mjg59@google.com>,
jamorris@linux.microsoft.com, sashal@kernel.org,
kgoldman@us.ibm.com, "Wiseman, Monty (GE Global Research,
US)" <monty.wiseman@ge.com>,
Roberto Sassu <roberto.sassu@huawei.com>
Subject: Re: [PATCH 0/1] KEYS: Measure keys in trusted keyring
Date: Mon, 9 Sep 2019 14:34:54 -0700 (PDT) [thread overview]
Message-ID: <alpine.LRH.2.21.1909091429050.19397@namei.org> (raw)
In-Reply-To: <1568035881.4614.347.camel@linux.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 1034 bytes --]
On Mon, 9 Sep 2019, Mimi Zohar wrote:
> The remote attestation server could gate any service based on the
> certificate signer. The first gated service, based on this feature,
> will probably be network access (eg. TNC). If/when this feature is
> upstreamed, every company, including financial institutes,
> organizations, and governments will become THE certificate signer for
> their organization, in order to limit access to their network and
> systems.
This is already happening at scale, and a primary use-case for the
patchset.
> Once that happens, how long will it be until the same
> feature will be abused and used to limit the individual's ability to
> pick and choose which applications may run on their systems.[1]
Isn't this already happening (in a non-abusive way) with mobile devices?
> Mimi
>
> [1] Refer to Richard Stallman's last paragraph https://www.gnu.org/phi
> losophy/can-you-trust.en.html
Please consider if you really want to be endorsing this individual.
--
James Morris
<jmorris@namei.org>
next prev parent reply other threads:[~2019-09-09 21:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-28 0:27 [PATCH 0/1] KEYS: Measure keys in trusted keyring Lakshmi Ramasubramanian
2019-08-28 0:27 ` [PATCH 1/1] " Lakshmi Ramasubramanian
2019-09-02 22:04 ` Mimi Zohar
2019-08-29 1:11 ` [PATCH 0/1] " Mimi Zohar
2019-08-30 2:43 ` Lakshmi Ramasubramanian
2019-08-30 18:41 ` Mimi Zohar
2019-09-03 15:54 ` Lakshmi Ramasubramanian
2019-09-09 13:31 ` Mimi Zohar
2019-09-09 21:34 ` James Morris [this message]
2019-09-19 13:18 ` Sasha Levin
2019-09-19 17:12 ` Mimi Zohar
2019-10-04 19:29 ` Lakshmi Ramasubramanian
2019-10-04 19:57 ` Mimi Zohar
2019-10-04 20:10 ` Lakshmi Ramasubramanian
2019-10-04 21:58 ` Mimi Zohar
2019-10-05 0:10 ` Lakshmi Ramasubramanian
2019-10-06 13:17 ` Mimi Zohar
2019-10-07 15:03 ` Lakshmi Ramasubramanian
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=alpine.LRH.2.21.1909091429050.19397@namei.org \
--to=jmorris@namei.org \
--cc=jamorris@linux.microsoft.com \
--cc=kgoldman@us.ibm.com \
--cc=linux-integrity@vger.kernel.org \
--cc=mjg59@google.com \
--cc=monty.wiseman@ge.com \
--cc=nramas@linux.microsoft.com \
--cc=roberto.sassu@huawei.com \
--cc=sashal@kernel.org \
--cc=zohar@linux.ibm.com \
/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;
as well as URLs for NNTP newsgroup(s).