3 ms·
> You can in some sense sum up the cryptographic competence of DNSSEC by observing, as you have, that many of its largest deployers still use RSA-1024. If you h
by danyork 12y ago
> You can in some sense sum up the cryptographic competence of DNSSEC by observing, as you have, that many of its largest deployers still use RSA-1024. If you have any actual interest in cryptography
... you could also help improve the DANE protocol. The DANE Working Group within the IETF is open to all. The mailing list is at:
https://www.ietf.org/mailman/listinfo/dane https://www.ietf.org/mailman/listinfo/dane
FYI, the working group will be meeting Tuesday afternoon (July 22) here at IETF 90 in Toronto, Canada, from 16:40-18:40 EDT. Agenda is:
https://datatracker.ietf.org/meeting/90/agenda/dane/ https://datatracker.ietf.org/meeting/90/agenda/dane/
Streaming audio is at:
http://ietf90streaming.dnsalias.net/ietf/ietf902.m3u http://ietf90streaming.dnsalias.net/ietf/ietf902.m3u
Jabber chat room at: dane@jabber.ietf.org
You're certainly welcome to show up and ask questions about the crypto involved. :-)
- tptacek 12y agoNo, RSA-1024 does not sum up the cryptographic problems of DNSSEC. If it did, I would have just said that. "Actual" interest in cryptography?
- axaxs 12y agoYou managed to successfully refute and argue with...yourself I think.
- danyork 12y ago>"Actual" interest in cryptography? I was replying to your reply and quoted part of your message and just snipped it off without really indicating that I had just ended it. The way it came out on the HN page it is hard to see that it was your message versus mine. :-(
- tptacek 12y agoRSA-1024 is an easy problem to fix; it's not baked into the protocol. Other crypto problems in DNSSEC, not so much, sorry.