3 ms·
I'd note that the circumstances surrounding Dragonfly have been controversial, and it did end up being RFC 7664 https://www.ietf.org/mail-archive/web/tls/curre
by zokier 8y ago
I'd note that the circumstances surrounding Dragonfly have been controversial, and it did end up being RFC 7664
https://www.ietf.org/mail-archive/web/tls/current/msg10962.html https://www.ietf.org/mail-archive/web/tls/current/msg10962.h...
https://www.ietf.org/mail-archive/web/cfrg/current/msg03554.html https://www.ietf.org/mail-archive/web/cfrg/current/msg03554....
https://www.ietf.org/mail-archive/web/cfrg/current/msg03736.html https://www.ietf.org/mail-archive/web/cfrg/current/msg03736....
There is plenty of more discussion on IETF mailing lists (and probably elsewhere too). Ultimately on a glance I can't say how trustworthy Dragonfly is because of the controversy. Perrin has obvious strong dislike for it, but that alone is not yet the end of the world.
- acqq 8y agoGood references, thanks. Some highlights of one: https://www.ietf.org/mail-archive/web/cfrg/current/msg03554.html https://www.ietf.org/mail-archive/web/cfrg/current/msg03554.... "I'd like to request the removal of Kevin Igoe from CFRG co-chair." "Twice Kevin suggested a technique for deriving the Dragonfly password-based element which would make the protocol easy to break [IGOE_1, IGOE_2]. He also endorsed an ineffective attempt to avoid timing attacks by adding extra iterations to one of the loops [IGOE_3, IGOE_4]." Note that Kevin Igoe's mail address is "at nsa.gov" and all the quoted "accidents" happened before Snowden disclosures (which were in the Summer of 2013).