Subject: Re: binary for NetBSD Security Advisory 2003-009: sendmail
To: Jeremy C. Reed <email@example.com>
From: David Maxwell <firstname.lastname@example.org>
Date: 04/07/2003 22:22:41
On Mon, Apr 07, 2003 at 02:46:53PM -0700, Jeremy C. Reed wrote:
> I see that the
> advisory mentions a sendmail binary fix.
> This is great.
> But it mentions "file" as part of filename and what it replaces (instead
> of "sendmail"). (This did make me realize that a binary was also supplied
> for recent file(1) issue too.)
Oops. Yes, this is a trial run - which hopefully will become a regular
practice. We don't have binary patches as part of the template yet, that's
why I missed the s/file/sendmail/ in there...
> Also, the tar needs the "p" switch in that example.
Added. Thank You.
> Jeremy C. Reed
> p.s. By the way, I have been been building binary updates for NetBSD/i386
> for over a year and supply them for several customers.
> It would be nice if NetBSD always provided the fixes in binary formats.
I'm curious how you've gone about building the lists of files that need
to be updated - anything automated, or do you do it all manually?
With resources like releng.netbsd.org, getting the binaries for all the
architectures is now possible - it's still a fair bit of manual effort
for each SA though...
David Maxwell, email@example.comfirstname.lastname@example.org -->
Any sufficiently advanced Common Sense will seem like magic...