• 0 Posts
  • 12 Comments
Joined 3 months ago
cake
Cake day: June 4th, 2025

help-circle

  • I’m not sure if I agree.

    You can’t easy man in the middle authenticated protocols like SSH or HTTPS.

    Unless you own a CA, or are a powerful country able to coerce a CA, or mandate installing one into users’ PCs.

    As for SSH - you missed the “TOFU” bit, Trust On First Use. Do you verify your SSH host keys every time before connecting to a new server? The docs for GitHub doesn’t even mention it.

    unencrypted/unauthenticated protocols are on their death bed.

    I partially agree - encryption appears to be a solved problem today. Key distribution, however is not, it’s layers upon layers of half-solutions of wishful thinking, glued together with hope.

    The layers should be independent to allow for maximum flexibility.

    Depends on your threat model and priorities, right :) HPKP is helpful and does not require DNSSEC. DANE and CAA are helpful but require DNSSEC.




  • I’m fortunate to get native IPv6, so I’m not very familiar, tho I think I have basic understanding.

    Did you mean you need to pick just one of {authoritative DNS server, DNS64} to listen on port 53? No, because the authoritative DNS only needs to be accessible from the outside. Run it on another machine or nonstandard port, then expose via port forwarding. Machines in LAN don’t need direct access to the authoritative DNS server, they can just as well resolve via the regular system.