06.06.2016 13:04, Vladimir Sharun пишет:
Всем привет,
3.7 Computing the Message Hashes
Both signing and verifying message signatures start with a step of computing
two cryptographic hashes over the message. Signers will choose the parameters
of the signature as described in Signer Actions (Section 5); verifiers will use
the parameters specified in the DKIM-Signature header field being verified. In
the following discussion, the names of the tags in the DKIM-Signature header
field that either exists (when verifying) or will be created (when signing) are
used. Note that canonicalization (Section 3.4) is only used to prepare the
email for signing or verifying; it does not affect the transmitted email in any
way.
The signer/verifier MUST compute two hashes, one over the body of the message
and one over the selected header fields of the message. Signers MUST compute
them in the order shown. Verifiers MAY compute them in any order convenient to
the verifier, provided that the result is semantically identical to the
semantics that would be the case had they been computed in this order.
In hash step 1, the signer/verifier MUST hash the message body, canonicalized using the body canonicalization
algorithm specified in the "c=" tag and then truncated to the length specified in the
"l=" tag. That hash value is then converted to base64 form and inserted into (signers) or compared
to (verifiers) the "bh=" tag of the DKIM-Signature header field.
http://dkim.org/specs/rfc4871-dkimbase.html#hashing
Спасибо.
Теперь хотелось бы понять, что выполняется раньше шифрование через DKIM
или transport_filter?
_______________________________________________
Exim-users mailing list
Exim-users@mailground.net
http://mailground.net/mailman/listinfo/exim-users
