Dave Hart wrote: > On Sat, Oct 10, 2009 at 2:06 PM, Pierre Dubuc wrote: >> I get an OpenSSL error in my event log when launching 4.2.5p231-RC. >> >> Quote: >> >> The description for Event ID ( 0 ) in Source ( OPENSSL ) cannot be found. >> The local computer may not have the necessary registry information or >> message DLL files to display messages from a remote computer. You may be >> able to use the /AUXSOURCE= flag to retrieve this description; see Help and >> Support for details. The following information is part of the event: >> OPENSSL_Uplink(100F1020,05): no OPENSSL_Applink >> >> End quote. > > Those binaries were built against OpenSSL 0.9.8j. I installed 0.9.8k > just now and rebuilt the 4.2.5p231-RC .zip files I posted earlier with > it. Hopefully that will solve your problem. > > 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. I also strongly recommend that it never be copied to system32 but be placed in the same directory as the ntpd binary. Danny -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. _______________________________________________ questions mailing list [email protected] https://lists.ntp.org/mailman/listinfo/questions
