Date: Sat, 4 Aug 2001 21:42:28 -0700 From: Kris Kennaway <kris@obsecurity.org> To: Ollivier Robert <roberto@eurocontrol.fr> Cc: FreeBSD Current Users' list <freebsd-current@FreeBSD.ORG> Subject: Re: ntpd 4.1 Message-ID: <20010804214228.B8558@xor.obsecurity.org> In-Reply-To: <20010802122513.C89868@caerdonn.eurocontrol.fr>; from roberto@eurocontrol.fr on Thu, Aug 02, 2001 at 12:25:13PM %2B0200 References: <20010802122513.C89868@caerdonn.eurocontrol.fr>
next in thread | previous in thread | raw e-mail | index | archive | help
--ftEhullJWpWg/VHq Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Aug 02, 2001 at 12:25:13PM +0200, Ollivier Robert wrote: > Now that ntpd 4.1.0 has been released (finally!), I'll upgrade current ve= ry > soon. >=20 > The question I have is the following: authentication was done with md5 co= de > builtin and I disabled DES support (not supported anymore). Now, with 4.1, > it can be linked to openssl but it is still an optional component. >=20 > I'm a bit reluctant to force openssl for just ntpd. >=20 > Any ideas / comments ? What we do for a number of other system components that can be built with/without openssl/crypto support is to select that based on NO_OPENSSL (and some other -- semi-redundant -- checks), and make sure it's built twice in make release. Look at release/Makefile and the ppp and tcpdump code to see how it's done. Kris --ftEhullJWpWg/VHq Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE7bM6zWry0BWjoQKURAnD1AJ9eIki8cfr80VcQuS54ChQSqsYUCACgmArl bwGlhChxLAwSUvq5KZ65daY= =99vw -----END PGP SIGNATURE----- --ftEhullJWpWg/VHq-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010804214228.B8558>