From owner-freebsd-security Wed Aug 18 8:11: 7 1999 Delivered-To: freebsd-security@freebsd.org Received: from lariat.lariat.org (lariat.lariat.org [206.100.185.2]) by hub.freebsd.org (Postfix) with ESMTP id CFDF114E16 for ; Wed, 18 Aug 1999 08:11:04 -0700 (PDT) (envelope-from brett@lariat.org) Received: from mustang (IDENT:ppp0.lariat.org@lariat.lariat.org [206.100.185.2]) by lariat.lariat.org (8.9.3/8.9.3) with ESMTP id JAA08404; Wed, 18 Aug 1999 09:11:11 -0600 (MDT) Message-Id: <4.2.0.58.19990818090832.04805220@localhost> X-Sender: brett@localhost X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Wed, 18 Aug 1999 09:10:49 -0600 To: "Jordan K. Hubbard" , "James Gill" From: Brett Glass Subject: Re: OpenBSD Cc: freebsd-security@FreeBSD.ORG In-Reply-To: <78055.934964467@localhost> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 01:21 AM 8/18/99 -0700, Jordan K. Hubbard wrote: >It's never been a question of money, coordination, or really anything >at all to do with engineering. It has everything to do with one or >more individuals volunteering the time necessary for making something >like this happen. > >That also goes for just about every other obvious idea or clear >shortcoming that one might note for FreeBSD - if it's obvious or >clear, chances are excellent that it's been both suggested many times >and failed many times due to lack of this one key missing ingredient. :) With a larger (merged) talent pool, it'd be more likely to succeed. The biggest trick, of course, would be dealing with personalities, not code. I'll say this much, though: the OpenBSD approach to crypto export restrictions (i.e. keeping the code in Canada) is brilliant and could help FreeBSD. --Brett Glass To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message