TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

How to deal with bogus security reports?

1 点作者 ruik超过 4 年前
We started to receive a lot of questionable security reports to our security@domain mail. All are from India, all use gmail addresses. Usually they claim that there is no DMARC (but they did not bother to check SPF). Or they get 302 from our server and use &lt;!DOCTYPE HTML PUBLIC &quot;-&#x2F;&#x2F;IETF&#x2F;&#x2F;DTD HTML 2.0&#x2F;&#x2F;EN&quot;&gt; to claim: &quot;The information can be used by attackers for further finding of exploits and information gathering.&quot;<p>They are partly like scams, but reporting them to google gmail did not help. Any clue?

1 comment

lrvick超过 4 年前
Every bug program I have had any exposure to is mostly reports like these.<p>Once I started insisting researchers PGP encrypt their submissions to prevent leaks of potentially serious and sensitive issues... A side effect was it was easy to tell authentic reports from skiddy stuff.<p>No one with any significant security research experience has been able to avoid learning basic asymmetric cryptography... But the skiddies only want to copy paste from automated tools to hunt easy bounties.