3 ms·
What’s next? “Deprecating” ping by refusing to answer it? (Oh wait, everybody already does that.) Maybe the HTTP HEAD request? Or any other protocol than HT
by teddyh 12y ago
What’s next? “Deprecating” ping by refusing to answer it? (Oh wait, everybody already does that.) Maybe the HTTP HEAD request? Or any other protocol than HTTP, and any other packet type than TCP and UDP?
Standards are good and should be followed for good reasons. They allow for both diagnostics (is that host down or are ping packets just filtered?) and the development of new protocols (nope, can’t use SCTP or anything other than TCP or UDP; they might be filtered).
It seems like Cloudflare just wants ANY to simply go away since it would make their lives easier. Well, tough cookies, this is the Internet, and here we obey the standards. The standards do not change just to make your business model easier. Make your own standard or protocol if DNS is so broken that you can’t adhere to it.
Also, this: http://dnsreactions.tumblr.com/post/113952923614/when-cloudflare-tries-to-forbid-any http://dnsreactions.tumblr.com/post/113952923614/when-cloudf...
- rstupek 12y agoActually if you want to pass most PCI compliance scans, you have to not respond to HTTP HEAD requests.
- toomuchtodo 12y agoPCI compliance scans are, for the most part, a joke. If that's true, it's truly ridiculous.
- quicksilver03 12y agoHave you got a reference for that or it's based on your experience with PCI scan vendors?
- jlgaddis 12y agoIt would be in the PCI DSS [0]. [0]: https://www.pcisecuritystandards.org/security_standards/documents.php https://www.pcisecuritystandards.org/security_standards/docu...
- jamiesonbecker 12y ago"most?" Not in my experience, but anyway, that'd be really dumb. HEAD is extremely useful for checking etag caches. Failing to ask for a full HTTP body is not an exploitable security flaw. ;)
- geofft 12y ago> Standards are good and should be followed for good reasons. They allow for both diagnostics (is that host down or are ping packets just filtered?) and the development of new protocols (nope, can’t use SCTP or anything other than TCP or UDP; they might be filtered). That's a long way of saying "Be liberal in what you accept from others", which is a short way of saying "What security vulnerabilities? Everyone else on the ARPANET is a university researcher too, if they want an account on my system they can just ask." Standards should be followed if and only if you intend to support the specific thing being standardized. Implement the smallest, most robust subset of the standard that you need to to get the job done (in a future-proof way, mind you; don't just skip out on things because a certain remote implementation doesn't require you to care, that too is terrible for security). If the standard is well-written, that's all of it, but the older internet standards by and large weren't.
- teddyh 12y ago> “Everyone else on the ARPANET is a university researcher too […]” Strawman. > “don't just skip out on things because a certain remote implementation doesn't require you to care,” Like Cloudflare wants to skip implementing ANY just because they wish it wasn’t in the standard? You don’t get to skip parts of the standard just because you claim it’s not “well-written”. If you care about standards, take part in the standardization work. If the current standards are bad, work on new replacements. You don’t get to pick and choose what to implement if a standards says it’s a MUST. If Cloudflare does this, they don’t get to call what they are offering “DNS”; it’s “CloudflareNS”, and they should get their own port number.