DNSSEC PKI does not preclude one from hardcoding specific keys in the client as well.
replyProviding global PKI and enabling end-to-end authentication by default for all clients and protocols certainly would make the internet a safer place.
So now we're running two PKIs? What does the second one do? Why not three?
replyI would really appreciate it if you would respond to my points instead of just moving on to another argument.
replyDo you hardcode Github and AWS keys in your SSH config? Do you think it would be beneficial to global security if that happened automatically?
No, we run a fleet with thousands of physicals and hundreds of thousands of virtuals, of course we don't hardcode keys in our SSH configuration. Like presumably every other large fleet operator, we solve this problem with an internal SSH CA.
replyFurther, I haven't "moved on to another argument". Can you answer the question I just asked? If I have an existing internal PKI for my fleet, what security value is a trust relationship with DNSSEC adding? Please try to be specific, because I'm having trouble coming up with any value at all.