[exim-dev] [Bug 2180] DKIM oversigning

Page principale
Supprimer ce message
Répondre à ce message
Auteur: admin
Date:  
À: exim-dev
Sujet: [exim-dev] [Bug 2180] DKIM oversigning
https://bugs.exim.org/show_bug.cgi?id=2180

Richard James Salts <exim@???> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |exim@???


--- Comment #2 from Richard James Salts <exim@???> ---
It strikes me you either want to oversign, or sign the header if it exists. So
if you change the current default to
+Content-Type : +Content-Transfer-Encoding : +MIME-Version : +References : \
+In-Reply-To : +Message-ID : +Date : +Subject : +To : +From : Sender : \
+Reply-To : +Cc : +Content-ID : +Content-Description : Resent-Date : \
Resent-From : Resent-Sender : Resent-To : Resent-Cc : Resent-Message-ID : \
List-Id : List-Help : List-Unsubscribe : List-Subscribe : List-Post : \
List-Owner : List-Archive

then we'd be signing Content-Type if it existed and adding an extra
Content-Type head in the h= field of the DKIM signature, and so on. Those
without the + would just be left with the signature for any headers that exist
(i.e. 0 for List-Id, etc unless it was a message generated by a mailing list).
Is there a use case for never sign? Don't you just omit the header from
dkim_sign_headers?

--
You are receiving this mail because:
You are on the CC list for the bug.