From owner-freebsd-security  Wed Jul 29 23:30:08 1998
Return-Path: <owner-freebsd-security@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id XAA12550
          for freebsd-security-outgoing; Wed, 29 Jul 1998 23:30:08 -0700 (PDT)
          (envelope-from owner-freebsd-security@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 XAA12544
          for <security@FreeBSD.ORG>; Wed, 29 Jul 1998 23:30:06 -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 CAA22779;
	Thu, 30 Jul 1998 02:34:19 -0400 (EDT)
Date: Thu, 30 Jul 1998 02:34:19 -0400 (EDT)
From: andrewr  <andrewr@slack.net>
To: Garance A Drosihn <drosih@rpi.edu>
cc: security@FreeBSD.ORG
Subject: Re: FreeBSD Security How-To (Was: QPopper exploit)
In-Reply-To: <v04011703b1e51e26f888@[128.113.24.47]>
Message-ID: <Pine.NEB.3.96.980730023247.26994A-100000@brooklyn.slack.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-security@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


Ok, here is my solution.. All those interested in being on a FreeBSD
Security Audit mailing list, just email andrewr@slack.net and we can
figure out a way that we can do this not through FreeBSD.org.  After
speaking with jkh, we must first set up our own mailing list, then, if
productive, we can move it to FreeBSD.org.  But, for now, just email me.
And I will figure something out.

Andrew


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe security" in the body of the message