Binary Security Updates
Ok, I've decided that my binary security updates code is now release-worthy. Right now I'm only building updates for 4.7-RELEASE; as soon as 4.8-RELEASE comes out I'll start building updates for that as well. Note that this code only works properly if you performed a binary install of the -RELEASE and have not recompiled anything (ie, haven't applied any updates since October), so theoretically nobody should be using this until after 4.8 is released. Everything is at http://www.daemonology.net/freebsd-update/ including a portified version of the client and the resulting package. MD5 hashes are dac0f4bdf3d23b642bcbbac0e544821e, 12f69c9d0a2bf1f5278e49f0a4821aa7, b96bfc6bffcbfa18130250e36e6109d6, and 227819b9403a6f727566bd6ad5a79684 for server, client, client port, and client package respectively. Feedback is welcome. ;) Colin Percival PS. This is probably of interest to people reading stable@ as well, but that would apparently constitute excessive cross-posting. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Binary security updates
On Sunday 16 February 2003 02:39, Colin Percival wrote: >On december 25th, I released a "first draft" of a binary security > update tool aimed at allowing people to track the security branches > without keeping a source tree or recompiling; the response was generally > positive, but as I pointed out in my announcement, there were several > problems which needed to be fixed. >I'm just about finished fixing up all those details, and I intend to > release a new version soon and start publishing the necessary updates for > i386 4.8-RELEASE when it comes out (not that I expect 4.8-RELEASE to > include any security holes, of course ;). These would, of course, be > freely available (although I might ask for donations to cover bandwidth > costs if I get lots of traffic). >Would any FreeBSD developer(s) be willing to help me with this? I'd > very much like to have at least one person look over my code and give it > some sort of "stamp of approval"; both for my own peace of mind and to > make people feel more happy about using it. If you are willing to do the work, I'm certain we can track down some mirror sites willing to bear the traffic for you. We'll bring the efforts of the Donations Liason Officer, Michael W. Lucas, to bear on this. All you need to do is let him know what resources you will need. -- Where am I, and what am I doing in this handbasket? Wes Peters [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Binary security updates
On december 25th, I released a "first draft" of a binary security update tool aimed at allowing people to track the security branches without keeping a source tree or recompiling; the response was generally positive, but as I pointed out in my announcement, there were several problems which needed to be fixed. I'm just about finished fixing up all those details, and I intend to release a new version soon and start publishing the necessary updates for i386 4.8-RELEASE when it comes out (not that I expect 4.8-RELEASE to include any security holes, of course ;). These would, of course, be freely available (although I might ask for donations to cover bandwidth costs if I get lots of traffic). Would any FreeBSD developer(s) be willing to help me with this? I'd very much like to have at least one person look over my code and give it some sort of "stamp of approval"; both for my own peace of mind and to make people feel more happy about using it. Colin Percival To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message