Re: libar

From: Scott Kitterman <ietf-dkim_at_kitterman.com>
Date: Sun, 15 Jul 2012 22:10:50 -0400

On Sunday, July 15, 2012 03:56:12 PM Murray S. Kucherawy wrote:
> Fellow OpenDKIM users,
>
> We are considering discontinuing support for libar. The primary reasons for
> this are:
>
> - the standard bind resolver is thread-safe these days (or so we're told)
>
> - unbound, for which we have support, does everything libar does as well as
> including DNSSEC support and thread-safe modes
>
> - adding libar to DNSSEC is a non-trivial notion, and would also seem to be
> redundant
>
> - having one less thing to maintain is a Good Thing(tm)
>
> - putting our support behind unbound will encourage DNSSEC deployment
>
> What sort of hardship would be created if this decision were to be made for
> 2.7.0? We would likely make this release in the last quarter of this year.
>
> Comments, please.

In Debian/Ubuntu, unbound has been used since opendkim 1.0 (which is the first
to appear in the package archives). Ubuntu also used unbound with opendkim's
predecessor, dkim-milter. I don't recall this ever being a problem.

It sounds like a good move to me and there's certainly no downside from my
perspective.

Scott K
Received on Mon Jul 16 2012 - 02:11:04 PST