From owner-freebsd-current Thu Sep 10 08:19:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA13589 for freebsd-current-outgoing; Thu, 10 Sep 1998 08:19:46 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from brooklyn.slack.net (brooklyn.slack.net [206.41.21.102]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA13565; Thu, 10 Sep 1998 08:19:41 -0700 (PDT) (envelope-from andrewr@brooklyn.slack.net) Received: from localhost (andrewr@localhost) by brooklyn.slack.net (8.8.7/8.8.7) with SMTP id LAA16903; Thu, 10 Sep 1998 11:20:10 -0400 (EDT) Date: Thu, 10 Sep 1998 11:20:10 -0400 (EDT) From: andrewr To: Enkhyl cc: security@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: FreeBSD Hardening In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 9 Sep 1998, Enkhyl wrote: > Back when the popper buffer overflow bug sprang forth it was suggested > that it might be a good idea to go through the OpenBSD change logs and > evaluate security-related fixes for inclusion in FreeBSD. Is there anyone > actively working on this? If there is a project organized around this, I'm > willing to help out with the endeavor. Otherwise, I'm willing to embark on > this endeavor and make a project out of it. This kind of died due to lack of interest. As I was told by jkh, if one is interested enough in this, just start up a mailing list (not from FreeBSD.org) and a team of workers and get to it. Soon, if all goes well, it would be incorporated into the actual project. Good luck. Andrew > > Comments? > > -- > Christopher Nielsen > Scient: The Art and Science of Electronic Business > cnielsen@scient.com > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-security" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message