per-entity - Re: [Per-Entity] implementing a cache on the client

Subject: Per-Entity Metadata Working Group

List archive

Re: [Per-Entity] implementing a cache on the client

From: "Cantor, Scott" <>
To: Jorj Bauer <>, Nick Roy <>, "" <>
Subject: Re: [Per-Entity] implementing a cache on the client
Date: Wed, 27 Jul 2016 21:51:16 +0000
Accept-language: en-US
Authentication-results: spf=pass (sender IP is 164.107.81.218) smtp.mailfrom=osu.edu; incommon.org; dkim=none (message not signed) header.d=none;incommon.org; dmarc=bestguesspass action=none header.from=osu.edu;
Spamdiagnosticmetadata: NSPM
Spamdiagnosticoutput: 1:99

On 7/27/16, 5:33 PM,
"
on behalf of Jorj Bauer"
<
on behalf of
>
wrote:

> - you've configured the endpoint to subvert TLS in some way (skip TLS
> validation, or install custom root certificate that pretends to be what
> it's not).

The trust model here is not TLS, it's a signature plus a lot of other
semantic detail around document expiration and limiting document validity,
same as in the aggregate case.

-- Scott

Re: [Per-Entity] implementing a cache on the client, (continued)

List archive

Re: [Per-Entity] implementing a cache on the client