blocks|key|3098734|text|我们有一系列用于webhook的IP，但随着我们的扩展，它们可以(并且很可能会)更改或添加新的IP。另一种方法是将查询字符串添加到您在Mandrill中添加的webhook+URL中，然后在收到帖子时检查该查询字符串，这样您就可以验证它是否来自Mandrill。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3098735|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

We have a range of IPs used for webhooks, but they can (and likely will) change or have new ones added as we scale. An alternative would be to add a query string to the webhook URL you add in Mandrill, and then check for that query string when a POST comes in so you can verify it's coming from Mandrill.

blocks|key|168547|text|Mandrill的签名位于HTTP响应头：Authenticating-webhook-requests|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|168548|在请求头中找到：X-Mandrill-Signature。这是哈希码的base64，使用web挂钩密钥签名。此密钥仅对您的webhook保密。|style|CODE|168549|entityMap|0|LINK|mutability|MUTABLE|url|https://mailchimp.com/developer/transactional/guides/track-respond-activity-webhooks/^0|L|V|0|0|8|K|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]]|C|$]]|$1|D|3|E|5|6|7|T|8|@$A|U|B|V|F|G]]|9|@]|C|$]]|$1|H|3|-4|5|6|7|W|8|@]|9|@]|C|$]]]|I|$J|$5|K|L|M|C|$N|O]]]]

Mandrill's signature is located in the HTTP response header: <a href="https://mailchimp.com/developer/transactional/guides/track-respond-activity-webhooks/" rel="nofollow noreferrer">Authenticating-webhook-requests</a>
In the request header find: <code>X-Mandrill-Signature</code>. This is a base64 of the hashcode, signed using web-hook key. This key is secret to your webhook only.

blocks|key|1313322|text|只需替换常量并使用此函数：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1313323|<?php+

function+generateSignature($post)
++++{
++++++++$signed_data+=+WEB_HOOK_URL;
++++++++ksort($post);
++++++++foreach+($post+as+$key+=>+$value)+{
++++++++++++$signed_data+.=+$key;
++++++++++++$signed_data+.=+$value;
++++++++}

++++++++return+base64_encode(hash_hmac('sha1',+$signed_data,+WEB_HOOK_AUTH_KEY,+true));
++++}

//---

if+(generateSignature($_POST)+!=+$_SERVER['HTTP_X_MANDRILL_SIGNATURE'])+{
++++//Invalid
}

?>|code-block|syntax|javascript|1313324|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

Just replace the constants and use this function:

<pre><code>&lt;?php 

function generateSignature($post)
 {
 $signed_data = WEB_HOOK_URL;
 ksort($post);
 foreach ($post as $key =&gt; $value) {
 $signed_data .= $key;
 $signed_data .= $value;
 }

 return base64_encode(hash_hmac('sha1', $signed_data, WEB_HOOK_AUTH_KEY, true));
 }

//---

if (generateSignature($_POST) != $_SERVER['HTTP_X_MANDRILL_SIGNATURE']) {
 //Invalid
}

?&gt;
</code></pre>

blocks|key|1309498|text|正如在mandrill的docs中所描述的，它们提供一个签名来检查请求是否真的来自它们。要构建请求，有几个步骤：|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1309499|1309500|从web钩子的确切url开始(斜杠和参数)|ordered-list-item|1309501|按键对post变量进行排序(在mandrill的情况下，您将只有一个post参数：|1309502|键和url的值，没有任何分隔符|1309503|hmac将url与您的密钥(您可以从web界面获取密钥)进行base64。|1309504|将结果与X-Mandrill-Signature标题<代码>H213<代码>G214进行比较|style|CODE|1309505|1309506|下面是一个用python实现的示例：|1309507|import+hmac,+hashlib

def+check_mailchimp_signature(params,+url,+key):
++++signature+=+hmac.new(key,+url,+hashlib.sha1)
++++for+key+in+sorted(params):
++++++++signature.update(key)
++++++++signature.update(params[key])
++++return+signature.digest().encode("base64").rstrip("\n")|code-block|syntax|javascript|1309508|entityMap|0|LINK|mutability|MUTABLE|url|https://mandrill.zendesk.com/hc/en-us/articles/205583257-Authenticating-webhook-requests^0|C|4|0|0|0|0|0|0|0|4|K|0|0|0|0^^$0|@$1|2|3|4|5|6|7|17|8|@]|9|@$A|18|B|19|1|1A]]|C|$]]|$1|D|3|-4|5|6|7|1B|8|@]|9|@]|C|$]]|$1|E|3|F|5|G|7|1C|8|@]|9|@]|C|$]]|$1|H|3|I|5|G|7|1D|8|@]|9|@]|C|$]]|$1|J|3|K|5|G|7|1E|8|@]|9|@]|C|$]]|$1|L|3|M|5|G|7|1F|8|@]|9|@]|C|$]]|$1|N|3|O|5|G|7|1G|8|@$A|1H|B|1I|P|Q]]|9|@]|C|$]]|$1|R|3|-4|5|6|7|1J|8|@]|9|@]|C|$]]|$1|S|3|T|5|6|7|1K|8|@]|9|@]|C|$]]|$1|U|3|V|5|W|7|1L|8|@]|9|@]|C|$X|Y]]|$1|Z|3|-4|5|6|7|1M|8|@]|9|@]|C|$]]]|10|$11|$5|12|13|14|C|$15|16]]]]

As described in mandrill's <a href="https://mandrill.zendesk.com/hc/en-us/articles/205583257-Authenticating-webhook-requests" rel="nofollow noreferrer">docs</a>, they provide a signature to check if the request really came from them. to build the request there's a few steps:

<ol>
<li>start with the exact url of your webhook (mind slashes and params)</li>
<li>sort the post variables by key (in case of mandrill, you'll only have one post parameter: <code>mandrill_events</code>)</li>
<li>add key and value to the url, without any delimiter</li>
<li>hmac the url with your secret key (you can get the key from the web-interface) and base64 it.</li>
<li>compare the result with the <code>X-Mandrill-Signature</code> header</li>
</ol>

here's a sample implementation in python:

<pre><code>import hmac, hashlib

def check_mailchimp_signature(params, url, key):
 signature = hmac.new(key, url, hashlib.sha1)
 for key in sorted(params):
 signature.update(key)
 signature.update(params[key])
 return signature.digest().encode("base64").rstrip("\n")
</code></pre>

blocks|key|3098803|text|205.201.136.0/16|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3098804|我刚刚在我的服务器防火墙中将它们列入了白名单。|3098805|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

205.201.136.0/16

I have just whitelisted them in my server's firewall.

blocks|key|3098947|text|我们不需要将他们正在使用的Ip列入白名单。取而代之的是，他们提供了自己的方法来验证webhook请求。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3098948|当您创建mandrill+webhook时，它将生成密钥。它将出现在响应中，我们正在得到我们的帖子URL，这是在webhook中提供的。|3098949|public+async+Task<IHttpActionResult>+MandrillEmailWebhookResponse()
++++++++{
++++string+mandrillEvents+=+HttpContext.Current.Request.Form["mandrill_events"].Replace("mandrill_events=",+"");

++++++++++++++++//+validate+the+request+is+coming+from+mandrill+API
++++++++++++++++string+url+=+ConfigurationManager.AppSettings["mandrillWebhookUrl"];
++++++++++++++++string+MandrillKey+=+ConfigurationManager.AppSettings["mandrillWebHookKey"];
++++++++++++++++url+%2B=+"mandrill_events";
++++++++++++++++url+%2B=+mandrillEvents;
++++++++++++++++byte[]+byteKey+=+System.Text.Encoding.ASCII.GetBytes(MandrillKey);
++++++++++++++++byte[]+byteValue+=+System.Text.Encoding.ASCII.GetBytes(url);

++++++++++++++++HMACSHA1+myhmacsha1+=+new+HMACSHA1(byteKey);
++++++++++++++++byte[]+hashValue+=+myhmacsha1.ComputeHash(byteValue);
++++++++++++++++string+generatedSignature+=+Convert.ToBase64String(hashValue);

++++++++++++++++string+mandrillSignature+=+HttpContext.Current.Request.Headers["X-Mandrill-Signature"].ToString();

++++++++++++++++if+(generatedSignature+==+mandrillSignature)
++++++++++++++++{
++++++++++++++++++++//+validation+=+"Validation+successful";
++++++++++++++++++++//+do+the+updating+using+the+response+data
++++++++++++++++}
}|code-block|syntax|javascript|3098950|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|L|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|M|8|@]|9|@]|A|$G|H]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

We don't need to white list the Ip they are using. Instead of that they have provided their own way to authenticate the webhook request.

When you are creating the mandrill webhook it will generate the key. It will come under the response we are getting to our post URL which is provided in the webhook.

<pre><code>public async Task&lt;IHttpActionResult&gt; MandrillEmailWebhookResponse()
 {
 string mandrillEvents = HttpContext.Current.Request.Form["mandrill_events"].Replace("mandrill_events=", "");

 // validate the request is coming from mandrill API
 string url = ConfigurationManager.AppSettings["mandrillWebhookUrl"];
 string MandrillKey = ConfigurationManager.AppSettings["mandrillWebHookKey"];
 url += "mandrill_events";
 url += mandrillEvents;
 byte[] byteKey = System.Text.Encoding.ASCII.GetBytes(MandrillKey);
 byte[] byteValue = System.Text.Encoding.ASCII.GetBytes(url);

 HMACSHA1 myhmacsha1 = new HMACSHA1(byteKey);
 byte[] hashValue = myhmacsha1.ComputeHash(byteValue);
 string generatedSignature = Convert.ToBase64String(hashValue);

 string mandrillSignature = HttpContext.Current.Request.Headers["X-Mandrill-Signature"].ToString();

 if (generatedSignature == mandrillSignature)
 {
 // validation = "Validation successful";
 // do the updating using the response data
 }
}
</code></pre>

For security purposes, I try to allow only Mandrill's IP(s) to access these urls.
Does anyone know them?

Mandrill Webhooks - Security

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云AI代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

功能1上新10个字符

功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符。

功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符。

功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符

功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符

功能4上新

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

精选全网热门MCP server，让你的AI更好用 🚀

💥开发者 MCP广场重磅上线！

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

出于安全考虑，我尝试只允许Mandrill的IP访问这些urls。有人认识他们吗？

问Mandrill Webhooks -安全
EN

回答 6

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Mandrill Webhooks -安全EN

回答 6

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Mandrill Webhooks -安全
EN