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

科技回声

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

GitHubTwitter

首页

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

资源链接

HackerNews API原版 HackerNewsNext.js

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

Most IT companies fail to serve security.txt for RFC 9116 in 2025

43 点作者 spyc3 个月前

5 条评论

temp08263 个月前
Been in or around tech my whole life and this is the first time I&#x27;ve heard of security.txt. This article is trying to shame or something over what even <a href="https:&#x2F;&#x2F;securitytxt.org&#x2F;" rel="nofollow">https:&#x2F;&#x2F;securitytxt.org&#x2F;</a> is calling &quot;A proposed standard...&quot;?
评论 #43237537 未加载
评论 #43254702 未加载
chillfox3 个月前
I really don’t get why you would want to serve security.txt, it just invites an avalanche of automated spam.
评论 #43237144 未加载
评论 #43238784 未加载
评论 #43263030 未加载
kaladin-jasnah3 个月前
Are these all IT companies? Mazda and Marantz certainly don&#x27;t seem like they&#x27;re IT companies.
评论 #43237099 未加载
评论 #43237255 未加载
评论 #43236963 未加载
MadVikingGod3 个月前
I want to start off with that I do think the goal of this RFC is a laudable one, and anything that follows shouldn&#x27;t be taken as a damnation of it. If you are on the fence if you should implement security.txt just do it.<p>This article is a large nothing burger. &quot;I sampled 50 companies, most of which are on the internet because they have to be, and most didn&#x27;t implement an IETF comment&quot;. If these were mostly tech focused companies, or heck security companies, sure it would make sense to shame them, but if there is a vulnerability in Ford&#x27;s website I would bet the impact is quite low. Hell this is so poorly thought out I want to go try it on the top 100 websites by volume and maybe try and find a top 100 tech websites.
parliament323 个月前
Meh. Well known records (robots.txt, everything under .well-known&#x2F;, etc) are meant to be used by automated systems IMO. The only automated system that would ever use this is email harvesters.<p>You can find our security contact in the whois record for our domain, or through the &quot;vulnerability reporting&quot; link in the footer of our homepage. Good enough.