From owner-freebsd-security Sat May 20 13:16:31 2000 Delivered-To: freebsd-security@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id B04F437B6A1; Sat, 20 May 2000 13:16:28 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from localhost (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id NAA90711; Sat, 20 May 2000 13:18:54 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: Kris Kennaway Cc: "Jordan K. Hubbard" , security@FreeBSD.org Subject: Re: The SecureBSD stuff is now available for download In-reply-to: Your message of "Sat, 20 May 2000 12:41:06 PDT." Date: Sat, 20 May 2000 13:18:54 -0700 Message-ID: <90708.958853934@localhost> From: "Jordan K. Hubbard" Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Actually, we shouldn't, because the license will contaminate any derived > work. Hmmm. I just read the license agreement (thanks for the prod) and I have to agree that it looks pretty scary. Still, most things in the security arena are "obvious" enough that one could just as easily get sued by someone claiming infringement whether you ever looked at their code or not. I don't think anyone since AT&T has tried to argue the "contamination" angle, they just sue you for infringing their ideas whether you were ever acquainted with those ideas before or not. In other words, we're probably already screwed from a strictly legal perspective, and I'm not even just talking about security. I wonder how many patents we're infringing without even knowing about it. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message