Re: DNSCurve implementation

I'd be interested in a follow up conversation sometime to see if we
can perhaps work on some of these goals together. 1 and 2 are outside
of our scope realistically. However 3 and 4 are items that we could
perhaps work on together. We use python quite extensively and would
have interest in creating portable DNS libraries for the community.

-brian



On Wed, Feb 24, 2010 at 2:04 PM, Matthew Dempsky <[email protected]> wrote:
> On Wed, Feb 24, 2010 at 4:35 AM, Brian <[email protected]> wrote:
>> I run an authoritative managed DNS service. I've been contemplating
>> DNSCurve since the beginning of the project, but lack of real-world
>> implementations and use prevented doing so.
>
> Yeah, unfortunately I've not devoted nearly as much time over the past
> few months to this as it deserves, and I'm trying to use our
> (OpenDNS's) announcement as motivation to actually get something
> usable out the door.
>
> In particular, I have a few projects in mind that I'm trying to figure
> out how to best prioritize:
>
>  1. Finish and release the DNSCurve forwarder prototype / reference
> implementation
>  2. Add native authoritative DNSCurve support to tinydns
>  3. Write a simple (i.e., slow) but easy to comprehend (e.g.,
> Python?) implementation to help people understand and test DNSCurve
>  4. Write a library to make it easier to integrate DNSCurve support
> into existing DNS software (e.g., decoding and encoding packets,
> recognizing encoded DNSCurve public keys)
>