From owner-freebsd-security Wed Sep 9 19:08:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA04019 for freebsd-security-outgoing; Wed, 9 Sep 1998 19:08:24 -0700 (PDT) (envelope-from owner-freebsd-security@FreeBSD.ORG) Received: from hillbilly.hayseed.net (hillbilly.hayseed.net [204.62.130.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA03998; Wed, 9 Sep 1998 19:08:21 -0700 (PDT) (envelope-from enkhyl@hayseed.net) Received: from hillbilly.hayseed.net (enkhyl@hillbilly.hayseed.net [204.62.130.2]) by hillbilly.hayseed.net (8.9.1/8.8.5) with SMTP id TAA09588; Wed, 9 Sep 1998 19:10:52 -0700 Date: Wed, 9 Sep 1998 19:10:52 -0700 (PDT) From: Enkhyl To: Mike Smith cc: security@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: FreeBSD Hardening In-Reply-To: <199809100103.SAA02559@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 9 Sep 1998, Mike Smith 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. > > There are at least a couple of people doing this on a casual basis. > Having a "process owner" would probably be an excellent idea. > > Go do it! And away we go... I'll see if I can manage to get a mailing list together to organize the effort and divide up the work (anyone have a server I can host the list on? :-) Anyone that is casually working on this, please speak up so that we can "projectize" this. Thanks! -- 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