Date: Thu, 26 Dec 2002 19:08:46 -0500 (EST) From: Adrian Filipi-Martin <adrian+freebsd-binup@ubergeeks.com> To: Colin Percival <colin.percival@wadham.ox.ac.uk> Cc: freebsd-binup@FreeBSD.ORG, <freebsd-stable@FreeBSD.ORG> Subject: Re: Binary security updates Message-ID: <20021226190441.D68788-100000@lorax.ubergeeks.com> In-Reply-To: <5.0.2.1.1.20021225125238.037cd840@popserver.sfu.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 25 Dec 2002, Colin Percival wrote: > I've put together a basic binary updates tool aimed at people who want > to track a security branch without keeping a source tree and > recompiling. I have tested this code to the best of my ability -- but > since I only have one FreeBSD box (and it's on the other side of the > world), that ability is rather limited. Interesting. I'm looking it over and perhaps you could answer one question for me quickly. How do you deal with .a-files? They may be identical excepting for their table of contents and md5's don't look into the archive. Also did you run into anything with respect to other archive/library file types? We built our own binary patch system for our appliances, but it's a bit specific to our appliance's needs. We were able to make certain simplifying statements such as no appliance includes compilation tools or libraries, so the .a-file problem went away. Adrian -- [ adrian@ubergeeks.com ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021226190441.D68788-100000>