From c6dd5951a15cf1be34c8794ffd6ca2657f34af27 Mon Sep 17 00:00:00 2001 From: Andrew Morgan Date: Thu, 25 Jul 2019 18:53:32 +0100 Subject: [PATCH] Clients can cache the hash details if they want to --- proposals/2134-identity-hash-lookup.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/proposals/2134-identity-hash-lookup.md b/proposals/2134-identity-hash-lookup.md index 72bc4e531..83b0dceb2 100644 --- a/proposals/2134-identity-hash-lookup.md +++ b/proposals/2134-identity-hash-lookup.md @@ -120,10 +120,10 @@ If hashing, the client appends the pepper to the end of the 3PID string. "denny@example.com email" -> "denny@example.com emailmatrixrocks" ``` -Clients SHOULD request this endpoint each time before performing a lookup, to -handle identity servers which may rotate their pepper values frequently. -Clients MUST choose one of the given `algorithms` values to encrypt the -3PID during lookup. +Clients can cache the result of this endpoint, but should re-request it +during an error on `/lookup`, to handle identity servers which may rotate +their pepper values frequently. Clients MUST choose one of the given +`algorithms` values to encrypt the 3PID during lookup. Clients and identity servers MUST support SHA-256 as defined by [RFC 4634](https://tools.ietf.org/html/rfc4634), identified by the value