From owner-freebsd-current@FreeBSD.ORG Sat Jul 17 18:30:26 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 081DB16A4CE for ; Sat, 17 Jul 2004 18:30:26 +0000 (GMT) Received: from ylpvm29.prodigy.net (ylpvm29-ext.prodigy.net [207.115.57.60]) by mx1.FreeBSD.org (Postfix) with ESMTP id B784443D46 for ; Sat, 17 Jul 2004 18:30:25 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (adsl-67-115-75-142.dsl.lsan03.pacbell.net [67.115.75.142]) i6HIUM0W026290; Sat, 17 Jul 2004 14:30:22 -0400 Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id B79C552850; Sat, 17 Jul 2004 11:30:22 -0700 (PDT) Date: Sat, 17 Jul 2004 11:30:22 -0700 From: Kris Kennaway To: Xin LI Message-ID: <20040717183022.GA64172@xor.obsecurity.org> References: <20040717153016.GA3805@frontfree.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="82I3+IH0IqGh5yIs" Content-Disposition: inline In-Reply-To: <20040717153016.GA3805@frontfree.net> User-Agent: Mutt/1.4.2.1i cc: current@FreeBSD.org Subject: Re: About ISC-cron X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Jul 2004 18:30:26 -0000 --82I3+IH0IqGh5yIs Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Jul 17, 2004 at 11:30:16PM +0800, Xin LI wrote: > Hi folks, >=20 > I have did a preliminary work on ISC-cron 4.1 for FreeBSD. I have noticed > that: > - Both FreeBSD and NetBSD have cron and friends based on cron 3.0 > with some respective local modifications. > - OpenBSD has adopted ISC cron 4.0b1 in early 2001. After that, > they have did several security and stablity related improvements > that IMO is valuable for us, too. > - There are some minor bugs in FreeBSD's cron that should be > fixed. (e.g. having */0 in crontab will cause a local DoS, > crontab does not remove temp files when it is abnormally > terminated, etc.) >=20 > I have Google'd the mailing list and found no discussion explaining why > we have not upgraded our cron and friends. Is there any discussion I > have missed? In other words, should I make these work a port, or a diff > against src/, when I have finished the whole thing? About the only reason in favour of keeping cron 3.0 would be if there are compatibility issues. However this is still a weak reason since this is 5.x-CURRENT. I think upgrading cron in src sounds like a good idea. Kris --82I3+IH0IqGh5yIs Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFA+XA+Wry0BWjoQKURAq8CAKDUa6b2PvS9D301rYph77bupHbWEQCglgC1 QYKmTS0CwgHgw5DO/imwE0k= =ieGQ -----END PGP SIGNATURE----- --82I3+IH0IqGh5yIs--