Date: Fri, 24 Jul 2015 07:18:52 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 201738] [PATCH] ntpd Makefile links both libmd and libcrypto. Message-ID: <bug-201738-8-g4XqlMHP6I@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-201738-8@https.bugs.freebsd.org/bugzilla/> References: <bug-201738-8@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201738 John Marshall <John.Marshall@riverwillow.com.au> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #159041|0 |1 is obsolete| | --- Comment #2 from John Marshall <John.Marshall@riverwillow.com.au> --- Created attachment 159131 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=159131&action=edit Modified patch also removes LIBMD from DPADD line Built 10.2-BETA2 with this second patch (spurious LIBMD removed from both LDADD and DPADD lines) on two servers and two clients. ntpd crypto works fine for me now. The particular scenario is two NTP servers providing authenticated time via IPv6 multicast (with Autokey) to a multiple-segment LAN. All host keys were built with ntp-keygen using default settings (RSA-MD5) and IFF parameter files generated on the servers were copied to the keys directory on each of the clients. The clients were configured to use their host keys and listen on the IPv6 multicast address (multicastclient). ntpq> hostnames no ntpq> apeers remote refid assid st t when poll reach delay offset jitter ============================================================================== *2001:8000:1000: ca068376 1069 2 b 2 64 377 0.655 0.721 0.035 +2001:8000:1000: dffc2009 1070 2 b 12 64 376 0.589 -0.165 0.153 ntpq> associations ind assid status conf reach auth condition last_event cnt =========================================================== 1 1069 761a no yes ok sys.peer sys_peer 1 2 1070 741a no yes ok candidate sys_peer 1 ntpq> -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-201738-8-g4XqlMHP6I>