On Thu, Oct 29, 2009 at 2:48 AM, Danny Mayer <[email protected]> wrote: > Dave Hart wrote: >> ntpd builds on Windows shouldn't be so tightly-bound to the OpenSSL >> version they're built against. A solution has been proposed by Martin >> Burnicki in http://bugs.ntp.org/1302 but it has not been implemented >> yet. > > Not for this. There is no way to do this since the dll order is not > guaranteed. You have to ship the dll of the version that you built with.
In the two weeks since this email was written, the bug 1302 applink fix has gone in. I have no idea what makes you think the DLL load order is not guaranteed. The order is spelled out in gory detail in the remarks section of the LoadLibraryEx documentation: http://msdn.microsoft.com/en-us/library/ms684179(VS.85).aspx As for shipping DLLs I build with, that is not practical as inane US export restrictions on crypto prevent me from "shipping" any OpenSSL DLLs to go with the NTP binaries I post. With the bug 1302 applink change in place, your comments notwithstanding, I have every reason to believe it's doing as designed and allowing those with slightly different OpenSSL DLLs to run my binaries. > I also strongly recommend that it never be copied to system32 but be > placed in the same directory as the ntpd binary. Good advice. Cheers, Dave Hart _______________________________________________ questions mailing list [email protected] https://lists.ntp.org/mailman/listinfo/questions
