[exim-cvs] DKIM: Force use of tainted mem for headers

Top Page
Delete this message
Reply to this message
Author: Exim Git Commits Mailing List
Date:  
To: exim-cvs
Subject: [exim-cvs] DKIM: Force use of tainted mem for headers
Gitweb: https://git.exim.org/exim.git/commitdiff/044152b326039eaaefc45e88ef501c4b7e615cef
Commit:     044152b326039eaaefc45e88ef501c4b7e615cef
Parent:     4729b6937b582a029147ba51298f5c300c5b1891
Author:     Jeremy Harris <jgh146exb@???>
AuthorDate: Sun Mar 14 17:37:11 2021 +0000
Committer:  Jeremy Harris <jgh146exb@???>
CommitDate: Sat Mar 20 00:17:51 2021 +0000


    DKIM: Force use of tainted mem for headers
---
 src/src/pdkim/pdkim.c | 1 +
 1 file changed, 1 insertion(+)


diff --git a/src/src/pdkim/pdkim.c b/src/src/pdkim/pdkim.c
index f683240..ca16e2b 100644
--- a/src/src/pdkim/pdkim.c
+++ b/src/src/pdkim/pdkim.c
@@ -1922,6 +1922,7 @@ if (dot_stuffing) ctx->flags = PDKIM_DOT_TERM;
/* The line-buffer is for message data, hence tainted */
ctx->linebuf = store_get(PDKIM_MAX_BODY_LINE_LEN, TRUE);
ctx->dns_txt_callback = dns_txt_callback;
+ctx->cur_header = string_get_tainted(36, TRUE);

return ctx;
}