4 ms·

Another thing to keep in mind with DNSSEC is that DNS has a 512 byte limit when using UDP. Anything higher than that requires a full TCP connection - pretty cos

Another thing to keep in mind with DNSSEC is that DNS has a 512 byte limit when using UDP. Anything higher than that requires a full TCP connection - pretty costly. Anyone know if progress is being made on using ECC instead of RSA for DNSSEC?

axaxs 11y ago
EDNS0 extends this to 4096, and it seems pretty well supported. You can use ECC in DNSSEC, though not many people do yet.
- tptacek 11y ago
  One reason they don't is that major DNSSEC validators have been seen rejecting ECC signatures. Also, however much ECC gets deployed in DNSSEC: * The roots and TLDs remain RSA-signed (until very recently, they were signed RSA-1024!) * Those RSA records are obsolete PKCS1v15 RSA * The ECC used by DNSSEC is NIST p- curve DSA; both that curve and that construction are also obsolete, and error-prone * There is virtually no chance any of this is going to change, since change would require coordinated updates to thousands of DNSSEC validators, which were --- against the advice of lots of people --- deployed aggressively and in advance of real demand, thus locking DNSSEC down to 1990s crypto despite the fact that it's first commercial use was in 2015. Thankfully, two of the four most popular browsers on the Internet have declared publicly that they're not going to support DNSSEC (or DANE, the DNSSEC CA replacement scheme). DNSSEC is a dead letter. People who are interested in DNS security should get to work designing SDNS or Secure-DNS or CryptoDNS or whatever the successor to DNSSEC will be called.
  - jevinskie 11y ago
    What is your opinion on DNScrypt? As far as I've seen it is somewhat the Yin to DNSSEC's Yang.
    - tptacek 11y ago
      DNSSEC is top-down. DNSCrypt is bottom-up. DNSSEC provides no value until the whole system works. DNSCrypt adds value even if just two systems use it. DNSSEC uses 1990s crypto. DNSCrypt uses 2010+ crypto. DNSSEC doesn't protect name resolution queries. DNSCrypt only protects name resolution queries.
    - axaxs 11y ago
      This wasn't directed at me and I'm not the crypto expert Mr. Ptacek is, but DNScrypt and DNSSEC really aren't related as they serve different functions. DNScrypt encrypts you the user, and your lookups. DNSSEC is meant to protect site owners by authenticated the answers given to resolvers.

axaxs 11y ago

EDNS0 extends this to 4096, and it seems pretty well supported. You can use ECC in DNSSEC, though not many people do yet.

tptacek 11y ago
One reason they don't is that major DNSSEC validators have been seen rejecting ECC signatures. Also, however much ECC gets deployed in DNSSEC: * The roots and TLDs remain RSA-signed (until very recently, they were signed RSA-1024!) * Those RSA records are obsolete PKCS1v15 RSA * The ECC used by DNSSEC is NIST p- curve DSA; both that curve and that construction are also obsolete, and error-prone * There is virtually no chance any of this is going to change, since change would require coordinated updates to thousands of DNSSEC validators, which were --- against the advice of lots of people --- deployed aggressively and in advance of real demand, thus locking DNSSEC down to 1990s crypto despite the fact that it's first commercial use was in 2015. Thankfully, two of the four most popular browsers on the Internet have declared publicly that they're not going to support DNSSEC (or DANE, the DNSSEC CA replacement scheme). DNSSEC is a dead letter. People who are interested in DNS security should get to work designing SDNS or Secure-DNS or CryptoDNS or whatever the successor to DNSSEC will be called.
- jevinskie 11y ago
  What is your opinion on DNScrypt? As far as I've seen it is somewhat the Yin to DNSSEC's Yang.
  - tptacek 11y ago
    DNSSEC is top-down. DNSCrypt is bottom-up. DNSSEC provides no value until the whole system works. DNSCrypt adds value even if just two systems use it. DNSSEC uses 1990s crypto. DNSCrypt uses 2010+ crypto. DNSSEC doesn't protect name resolution queries. DNSCrypt only protects name resolution queries.
  - axaxs 11y ago
    This wasn't directed at me and I'm not the crypto expert Mr. Ptacek is, but DNScrypt and DNSSEC really aren't related as they serve different functions. DNScrypt encrypts you the user, and your lookups. DNSSEC is meant to protect site owners by authenticated the answers given to resolvers.