On 11/19/24 00:25, Wei Chuang wrote:
On Sun, Nov 17, 2024 at 2:20 PM Bron Gondwana <[email protected]> wrote:And I do agree there needs to be a way to say "I made changes, and I'm not telling you how to undo them" as well.+1. My belief is that security gateways are a particularly complex case that needs this trust me bit. For example they may redact or encrypt content where it doesn't make sense to provide the original content for. When security gateways rewrite many URLs, it may become burdensome to encode and reverse, and downstream receivers are going to have to trust the gateway to make benign transformations. This can work because they already have a relationship with their security vendor. However a trust me bit in general introduces a security loophole hence receivers should use only in those limited well understood scenarios.
If I follow this, the use case is a Secure Email Gateway or SEG, to use a Gartner-ism, and is likely the last hop before delivery to the recipient ADMD or mailstore. So why is DKIM2's "it's complicated" flag more useful here than the configured exception for the service or gateway the receiving ADMD contracted with?
I believe there are already many sites that are configured to accept whatever their SEG/service is doing based on IP range, TLS certificate, etc. What makes this juice worth the squeeze?
--S.
_______________________________________________ Ietf-dkim mailing list -- [email protected] To unsubscribe send an email to [email protected]
