In article <mailman.1260.1341794709.63724.bind-us...@lists.isc.org>, Matthew Pounsett <m...@conundrum.com> wrote:
> On 2012/07/08, at 20:40, Doug Barton wrote: > > > On 07/08/2012 17:33, Matthew Pounsett wrote: > >> > >> On 2012/07/08, at 20:29, Matthew Pounsett wrote: > >> > >>> > >>> On 2012/07/08, at 20:26, Mark Andrews wrote: > >>> > >>>> > >>>> One can also build named w/o GOST support if one wants. We statically > >>>> link all the engines when building named on Windows. > >>> > >>> Unfortunately the port doesn't provide the config hooks to disable GOST > >>> support. > >> > >> Actually.. how do you go about doing that anyway? I was just taking a > >> look at writing a patch for the port to allow GOST to be turned off, but > >> BIND's configure script doesn't have any information in it about disabling > >> individual ciphers. > > > > I wouldn't accept it anyway. For better or worse, GOST is part of the > > protocol. > > Okay. > > So to answer my earlier question, what file were you talking about copying > into the chroot environment for BIND? The shared library. When you link dynamically, all the libraries have to be in $chroot/usr/lib. -- Barry Margolin Arlington, MA _______________________________________________ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
