From owner-freebsd-stable Tue Jun 9 13:41:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA00724 for freebsd-stable-outgoing; Tue, 9 Jun 1998 13:41:36 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: (from jmb@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA00690; Tue, 9 Jun 1998 13:41:20 -0700 (PDT) (envelope-from jmb) From: "Jonathan M. Bresler" Message-Id: <199806092041.NAA00690@hub.freebsd.org> Subject: Re: Matt Behrens: Re: kernel compile problem In-Reply-To: from "Kelley L." at "Jun 9, 98 04:13:15 pm" To: kosh@kosh.cococo.net (Kelley L.) Date: Tue, 9 Jun 1998 13:41:19 -0700 (PDT) Cc: woods@zeus.leitch.com, freebsd-stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kelley L. wrote: > > Which brings me to the question, how does one keep FreeBSD up to date > and secure? Wrong question, mainly concerned with just keeping it secure. > I use RedHat, and they have the updates to use to keep all the packages up > to date with security fixes. Does anything similar exist in FreeBSD. I'm a > little new, so I'm just not familiar with all the FreeBSDisms yet. subscribe to freebsd-security-notifications. take the steps specified whenever a security notification is issued. subscribing to freebsd-security and reading the mail would be an additional step....that way you get early warning on items that will be addressed via a security notification. jmb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message