3 ms·
We need a better alternative to DNSSEC. Its design is outdated and it's implementations can be very clunky. It's like HTML and Javascript in a way. However, it
by jeroenhd 4y ago
We need a better alternative to DNSSEC. Its design is outdated and it's implementations can be very clunky. It's like HTML and Javascript in a way.
However, it's the system we've got. Unless you do some kind of on-the-fly domain generation or an outdated DNS registrar, it's quite easy to enable and it helps prevent all kind of weird DNS malarkey for those that care about their internet security.
- tptacek 4y ago1. It's not the system we've got, because we don't got it. Less than 4% of .COM is signed. Virtually no important domains are signed, particularly at the companies with the largest security teams. The root DNSSEC keys could land on Pastebin tonight and nobody would need to be paged. 2. It's not quite easy to enable it. Evidence for that position: the litany of stories where companies have tried to enable it, like Slack did, and had multi-hour worldwide outages as a result.
- b112 4y agoThe worst is, computer clocks drift, and ntp's domains are signed, so if your clock drifts enough, you cannot update your time, because dnssec invaliates time server records. Good times. Seen more than one org disable dnnsec, in bind, because of this.
- wahern 4y agoYou would have the same issue with TLS or any other scheme. When OpenNTPD added TLS-authenticated constraints, I immediately began having problems on one of my PCEngines APU with a broken RTC (same model as all my other ones, but clock would always reset when power removed, no matter how many times I changed the battery). I had to disable TLS constraints. Eventually they added a special "trusted" qualifier to NTP server directives for bypassing constraint checking. Authenticated time synchronization faces intrinsic dilemmas no matter the technology.
- EricE 4y agoHmm - my discord client wasn't updating and I suspected it was something with DNS - tried all kinds of things. Turned dnssec off and BAM! discord immediatel updated. Sigh.
- jeroenhd 4y ago1. It's the system I've got. 57.8% of .nl domains are validated by DNSSEC, and those are the ones I use and it works great. 2. All I needed to do was enable a checkbox and paste a key (that I generated myself because I didn't want to hit the "generate" button) so I know it can be easy. Most companies aren't Slack or Google with their custom resolver setups and complicated cloud configurations.