4 ms·
But this DNSCrypt proposal is specifically claiming to be a "slight variation" on DJB's DNSCurve protocol and curve25519. It uses his NaCl library for implement
by marshray 15y ago
But this DNSCrypt proposal is specifically claiming to be a "slight variation" on DJB's DNSCurve protocol and curve25519. It uses his NaCl library for implementation too.
But looking at the DNSCrypt code on github, there's no indication of who actually wrote it. It has no attribution, no source code comments. Haven't found a protocol document either.
The author(s) were certainly meticulous though. The #includes are categorized according to their standardization origin (posix, C, internal) and alphabetized within those categories.
- tptacek 15y agoI'm not actually sticking up for DNSCrypt; they reached out to me awhile ago but I kind of stiffed them for review time --- it's been an especially busy month.
- marshray 15y agoYeah. I'm not one thing or another on it yet either. It's just kind of like a spaceship lands from planet OpenDNS and a CDROM rolled out containing the source for a new OpenBSD daemon (without the horns). And you may be right about (DJB circa 2011) developing a new secure hash function more reliably than a new protocol if you take away the requirement that it also perform significantly better than SHA-2.