Skip to content

Body digest not verified #20

Open
Open

Description

@bortzmeyer

It seems that changing the body, even when there is a Content-Digest: in the signed headers, does not invalidate the signature.

Activity

  1. jricher commented on Feb 10, 2025

    @jricher
    Contributor

    That's correct, as explained in RFC9421 §7.2.8 (https://www.rfc-editor.org/rfc/rfc9421.html#name-message-content) you have to validate the hash of the body separately from the signature. This tool doesn't calculate or verify the hash as it's not directly related to the signature, but I'd welcome a PR to add such functions here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions