3 ms·
The “fail to serve” wording in the headline is unnecessarily rage-baity. It’s an interesting proposal, but trying to shame people into adopting proposed things
by Aurornis 2y ago
The “fail to serve” wording in the headline is unnecessarily rage-baity.
It’s an interesting proposal, but trying to shame people into adopting proposed things is more likely to generate groans and disinterest in 2025 than to win converts.
- technion 2y agoI see these sort of things as a signal. I would personally encourage use internally, because I would like to signal towards the right sort of researchers. But when you conflate that with some sort of expectation or "minimum effort" and try to shame people with it you signal something else, particularly to people who disagree with the value of said standard. I've had people show me my domains on "DNSSEC Hall of shame" site and my opinion of that site's existence lowers every time.
- tptacek 2y agoWell, I mean, it's a self-parodying site, since almost every common domain you type into it fails the test. People calling you out for flunking on that site are saying something important about themselves, not about your security practice.
- spyc 2y agoPeople who spent hours finding the right security contacts for companies without luck would likely disagree. The key failure is not the single missing file, but that security contacts are too hard to find and the effect that has.
- tatersolid 2y agoMy org doesn’t host a security.txt file because the security@example.com email address been standardized since 1997: https://www.rfc-editor.org/rfc/rfc2142 https://www.rfc-editor.org/rfc/rfc2142
- spyc 2y agoThat's not a good reason to not host the file.