2 ms·
Before I pick apart the obvious points, keep this in mind: do you __need__ DNSSEC right now? Not would it be helpful or nice or make things a bit more secure, b
by peterwwillis 12y ago
Before I pick apart the obvious points, keep this in mind: do you __need__ DNSSEC right now? Not would it be helpful or nice or make things a bit more secure, but do you need it?
--
> 1. DNSSEC is better than no DNSSEC.
You can't use your argument to defend your argument; this is circular reasoning and therefore illogical.
Also, the commenter has no idea what protocols use crypto in what way as many of them are proprietary.
> 4. [...]There may need to be some software adjustments to fully accommodate DNSSEC. However, there currently exist several DNSSEC plugins, extensions, or modules for several end user browsers. Thus, the code base has already been started, making improvements and merging code bases is the next step.
This is like saying "Replacing cars with driverless cars just requires a software update". Yeah. On every car and road. No biggie. I'll put it all on my Visa.
> In short, if a devops can type a few characters in a DNS record, a devops can deploy DNSSEC within a few hours depending on the domain complexity.
You don't need to be "a devops" to make a DNS record change, but ideally you would call this person the domain name record owner or DNS administrator. This shows little understanding of how DNS is deployed in the real world.
> Generally #6 is specious.
If you consider "we have to upgrade our OS on all our systems - which may range from 1 to 100,000 depending on the organization - to gain a marginal amount of security we didn't need before" to be specious [assuming Windows comes with a validating stub resolver now].
> There is a vulnerability in DNSSEC, that is openly listed in the RFCs, that indicates subdomains are enumerated. [..] However, for simple domains with a few hosts, enumerated architectures should be a minor problem if a problem at all.
"Please ignore this information leak."
> This sockpuppet Anti-DNSSEC rant is inaccurate, incomplete, and presents a picture of DNSSEC that is unsupported factually, mathematically, and architecturally.
"I can't argue the point that we don't need DNSSEC, so let's just throw some hyperbole around and hope nobody notices I don't even try to prove my claims."