Daniel Kahn Gillmor <dkg@fifthhorseman.net> writes:
> The header-mask member of the per-message crypto object allows a
> clever UI frontend to mark whether a header was protected (or not).
> And if it was protected, it contains enough information to show useful
> detail to an interested user. For example, an MUA could offer a "show
> what this message's Subject looked like on the wire" feature in expert
> mode.
>
> As before, we only handle Subject for now, but we might be able to
> handle other headers in the future.
>
> Signed-off-by: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
> ---
> devel/schemata | 6 ++++++
> notmuch-show.c | 21 +++++++++++++++++++++
> test/T356-protected-headers.sh | 4 ++--
> 3 files changed, 29 insertions(+), 2 deletions(-)
>
> diff --git a/devel/schemata b/devel/schemata
> index 72feb7b7..9d3c8d30 100644
> --- a/devel/schemata
> +++ b/devel/schemata
> @@ -88,9 +88,15 @@ crypto = {
> status: sigstatus,
> # was the set of signatures described under encrypted cover?
> encrypted: bool,
> + # which of the headers is covered by sigstatus?
> + headers: [header_name*]
> },
> decrypted?: {
> status: msgdecstatus,
> + # map encrypted headers that differed from the outside headers.
> + # the value of each item in the map is what that field showed externally
> + # (maybe null if it was not present in the external headers).
> + header-mask: { header_name: string|null,*}
> }
I think you also need to add a definition for header_name to schemata
(in the same way that messageid is defined as a string).
The name "header-mask" is a bit generic, but I don't have my head in
this topic like you do. I was thinking of something like
"replaced-headers", but it's only a mild suggestion.
_______________________________________________
notmuch mailing list
notmuch@notmuchmail.org
https://notmuchmail.org/mailman/listinfo/notmuch