From owner-freebsd-current Mon Jul 30 14: 4:47 2001 Delivered-To: freebsd-current@freebsd.org Received: from obsecurity.dyndns.org (adsl-63-207-60-69.dsl.lsan03.pacbell.net [63.207.60.69]) by hub.freebsd.org (Postfix) with ESMTP id B46DF37B406 for ; Mon, 30 Jul 2001 14:04:43 -0700 (PDT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 9D56666B04; Mon, 30 Jul 2001 14:04:42 -0700 (PDT) Date: Mon, 30 Jul 2001 14:04:42 -0700 From: Kris Kennaway To: current@FreeBSD.ORG Cc: Dima Dorfman , Kris Kennaway Subject: Re: HEADS UP: new libmp imported Message-ID: <20010730140441.F68654@xor.obsecurity.org> References: <20010729151946.B96357@xor.obsecurity.org> <20010729224116.BCE563E31@bazooka.unixfreak.org> <20010730074433.E57400@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="gdTfX7fkYsEEjebm" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010730074433.E57400@dragon.nuxi.com>; from dev-null@NUXI.com on Mon, Jul 30, 2001 at 07:44:33AM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --gdTfX7fkYsEEjebm Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Jul 30, 2001 at 07:44:33AM -0700, David O'Brien wrote: > On Sun, Jul 29, 2001, Kris Kennaway wrote: > > > > installed. This would involve a repo copy of crypto/openssl/crypto/bn > > to contrib/openssl-bn or something, and I'd keep the two in sync with > > future vendor imports. >=20 > You're likely to get people saying "repo bloat". And it does seem a > little wrong to have two copies in the tree like that. >=20 > Just what programs are affected by this issue (ie, which use libmp)? I don't have the list to hand right now, but they all related to the "secure RPC" code which arguably should be in the crypto distribution anyway. > > can get it to work, so much the better. That said, right now > > everything that uses libmp could be considered `crypto' code, anyway, >=20 > I don't see anything wrong with that. At this point the `crypto' code > should be seen as virtually required. Originally was was "optional" > because of USA export laws. That is not an issue today. We've tried to take the position that the crypto collection is useful and installed by default, but that the system should be fully usable without it. Not everyone lives in the USA, and other countries still have repressive crypto laws which might otherwise prevent them from using FreeBSD. Kris --gdTfX7fkYsEEjebm Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE7ZcvoWry0BWjoQKURAqvoAJ0f3vhORlxfbwBenID/D2Apm8xvlACfcAty jYvtusjBpWnMac65iJjDRBM= =MkdR -----END PGP SIGNATURE----- --gdTfX7fkYsEEjebm-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message