From owner-freebsd-questions@FreeBSD.ORG Thu Dec 2 05:06:40 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 88AF916A4CE for ; Thu, 2 Dec 2004 05:06:40 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.203]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2652243D1D for ; Thu, 2 Dec 2004 05:06:40 +0000 (GMT) (envelope-from taosecurity@gmail.com) Received: by rproxy.gmail.com with SMTP id a36so768435rnf for ; Wed, 01 Dec 2004 21:06:39 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding; b=Im95gXGCXw3vRH7EIXuMVK/NcR1mM4PtsnNclzS52TdJIjFVfOz8k6e0DTci9bl/L3/l6+HUIuDcXo0UBTYIAzaG5+AChMhvFDwTYA9TbJwZjlnHz7K8dYifEf9gdK0mv/5wmDEdtPE8NSQBLOBTSd7FtCB7mVMedzgPSydWVj8= Received: by 10.38.75.28 with SMTP id x28mr613123rna; Wed, 01 Dec 2004 21:06:39 -0800 (PST) Received: by 10.38.209.11 with HTTP; Wed, 1 Dec 2004 21:06:39 -0800 (PST) Message-ID: <120ef053041201210677fdabbb@mail.gmail.com> Date: Thu, 2 Dec 2004 00:06:39 -0500 From: Richard Bejtlich To: freebsd-questions@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Answers: Keeping FreeBSD Up-To-Date X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Richard Bejtlich List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Dec 2004 05:06:40 -0000 Here's (hopefully) some answers for once, rather than more questions! I am happy to announce the publication at TaoSecurity.com of 'Keeping FreeBSD Up-To-Date': http://www.taosecurity.com/keeping_freebsd_up-to-date.html I wrote this article to answer questions I've received over the past few months on how to apply security fixes to a FreeBSD system. While the official Handbook is excellent, I thought a case-study approach would be enlightening for some readers. I thought it would be interesting to see a box begin life as FreeBSD 5.2.1 RELEASE, and then progress through a variety of security fixes applied in different ways. The article's sections include: - Introduction - FreeBSD Versions - Learning About Security Issues - Starting with the Installation - Binary OS and Userland Updates with FreeBSD Update - Applying Kernel Patches Manually - Applying Userland Patches Manually, Part 1 - Applying Userland Patches Manually, Part 2 - CVSup to 5_2 Security Branch - Beyond the Security Branch - STABLE: The End of the Line - The "Next" STABLE - Conclusion - Acknowledgements - References Sections show commands to run, explanations of what they do, sample output, uname versions, and pros and cons of each upgrade method. Please send feedback to taosecurity at gmail dot com. Thank you, Richard Bejtlich