Date: Mon, 30 Oct 2000 01:44:40 -0800 From: Kris Kennaway <kris@FreeBSD.ORG> To: Matt Heckaman <matt@ARPA.MAIL.NET> Cc: FreeBSD-SECURITY <freebsd-security@FreeBSD.ORG> Subject: Re: crontab problem Message-ID: <20001030014440.A11913@citusc17.usc.edu> In-Reply-To: <Pine.BSF.4.21.0010300109250.3528-100000@epsilon.lucida.qc.ca>; from matt@ARPA.MAIL.NET on Mon, Oct 30, 2000 at 01:10:15AM -0500 References: <Pine.BSF.4.21.0010300109250.3528-100000@epsilon.lucida.qc.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
--LQksG6bCIzRHxTLp Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Oct 30, 2000 at 01:10:15AM -0500, Matt Heckaman wrote: > Hi all, >=20 > Does anyone have a patch for the crontab problem describe on bugtraq? I > need to get it fixed and can't afford a make world. A patch or the pair > of revision numbers would be great, thanks. :) There was a patch posted to -audit a few days ago which is yet unreviewed but claims to address the issue. Note that we've been unable to replicate the claimed full impact of the problem on FreeBSD - the impact seems to be limited to reading files which are a valid cron job syntax, meaning basically files which are entirely commented out, or actual cron jobs (e.g. those owned by other users). Still a problem, though. Kris --LQksG6bCIzRHxTLp Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjn9QwcACgkQWry0BWjoQKV7OQCg0r7zKT84Zitsh8D68j+2IfPI omsAoPvGAAYJWyg1tKiAlvvk8yCzx/aj =cOv6 -----END PGP SIGNATURE----- --LQksG6bCIzRHxTLp-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20001030014440.A11913>