News for hackers. Stuff that matters.
Re:DNSSEC failures are how you get people to disable DNSSEC by silisili on Thursday June 01, 2023 @12:48AM (#36147672)
DNS is de facto decentralized. Stand up your own root, it's that simple.

DNSSEC has no bearing on how centralized something is - it works the same on the current system as it would on your own new DNS system.

Re:DNSSEC failures are how you get people to disable DNSSEC by noman-land on Thursday June 01, 2023 @12:52AM (#36147687)
Wait, what? How can I be my own certificate authority?
Re:DNSSEC failures are how you get people to disable DNSSEC by cyberax on Thursday June 01, 2023 @01:01AM (#36147723)
Create your own root certificate, import it into your browser, and into the OS certificate store. Then just sign CSRs with this root certificate's private key.

This is pretty much what all large corporations do for their internal infrastructure.

Re:DNSSEC failures are how you get people to disable DNSSEC by RandomBK on Thursday June 01, 2023 @01:19AM (#36147820)
This of course, only works for your own internal use. I feel this disclaimer needs to be called out explicitly.

If you're trying to do something that will be trusted by the global internet, you'll need to use an official CA, ergo the complaints of DNSSEC being too 'centralized'.

Re:DNSSEC failures are how you get people to disable DNSSEC by IcePic on Thursday June 01, 2023 @01:30AM (#36147874)
Then again, what the "global CAs" are doing is not wholly different in a technical level than what a company with their own internal CA does, except that I hope the global CAs take security very very seriously, and they pass an expensive audit.

In the end, it is just some company or organisation that creates a root CA cert and intermediaries, and then jump through hoops to make browsers and OS cert stores add their certs. Not saying it is easy, just that the technical parts are rather similar, the rest being a cumbersome way to prove you are trustworthy by showing off your processes and fences around the signing boxes.

Re:DNSSEC failures are how you get people to disable DNSSEC by RandomBK on Thursday June 01, 2023 @01:47AM (#36147936)
In the case of DNSSEC, the ultimate 'root key' is handled quite carefully and is interesting to read up on.

https://www.iana.org/dnssec/files

https://www.cloudflare.com/dns/dnssec/root-signing-ceremony/

Re:DNSSEC failures are how you get people to disable DNSSEC by detourdog on Thursday June 01, 2023 @05:36AM (#36149055)
One can distribute self signed ssl certificates. Not using a CA is more secure for the group relying on the certificates to maintain encryption.
Re:DNSSEC failures are how you get people to disable DNSSEC by conradev on Thursday June 01, 2023 @01:23AM (#36147841)
and, if you have a compelling reason, you can convince other CAs to cross-sign your certificate, like LetsEncrypt did: https://letsencrypt.org/2020/09/17/new-root-and-intermediate...

Browsers control what they trust, too, and can remove roots if they’re behaving poorly: https://blog.mozilla.org/security/2011/08/29/fraudulent-goog...

That is to further your point: there is no central decision-maker

Re:DNSSEC failures are how you get people to disable DNSSEC by detourdog on Thursday June 01, 2023 @05:38AM (#36149072)
Browser can also use self-signed certificates to trust lists.
Re:DNSSEC failures are how you get people to disable DNSSEC by silisili on Thursday June 01, 2023 @12:56AM (#36147701)
Openssl works just fine, if you're asking in earnest.

Either way, it has no bearing on DNS.