From owner-freebsd-security Wed Jul 5 22: 2:51 2000 Delivered-To: freebsd-security@freebsd.org Received: from caligula.anu.edu.au (caligula.anu.edu.au [150.203.224.42]) by hub.freebsd.org (Postfix) with ESMTP id 0159837B6D9; Wed, 5 Jul 2000 22:02:42 -0700 (PDT) (envelope-from avalon@caligula.anu.edu.au) Received: (from avalon@localhost) by caligula.anu.edu.au (8.9.3/8.9.1) id PAA03242; Thu, 6 Jul 2000 15:02:37 +1000 (EST) From: Darren Reed Message-Id: <200007060502.PAA03242@caligula.anu.edu.au> Subject: Re: SecureBSD (Was: Re: Firewalls and the endless story!) To: kris@FreeBSD.ORG (Kris Kennaway) Date: Thu, 6 Jul 2000 15:02:37 +1000 (Australia/ACT) Cc: cjclark@alum.mit.edu, sward@voltage.net (Susie Ward), freebsd-security@FreeBSD.ORG In-Reply-To: from "Kris Kennaway" at Jul 05, 2000 09:53:05 PM X-Mailer: ELM [version 2.5 PL1] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In some mail from Kris Kennaway, sie said: > > On Wed, 5 Jul 2000, Crist J. Clark wrote: > > > I don't see why you can't read the code. To my knowledge, none of the > > methods or algorithms have been patented by the SecureBSD > > people. Nothing to stop one from writing their own implementation of > > the same processes. Or have they gone for some patents? > > If I read the code, and then inadvertently use some concepts in my own > code they can try and claim it as a derived work and do nasty things to > me. There is a person working on an independant implementation for NetBSD of the "trusted binary" `problem'. AFAIK it has nothing to do with SecureBSD (unless they're using his code). Darren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message