From owner-freebsd-current Sun Feb 20 15: 6:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from peak.mountin.net (peak.mountin.net [207.227.119.2]) by hub.freebsd.org (Postfix) with ESMTP id 8D25837C078; Sun, 20 Feb 2000 15:06:40 -0800 (PST) (envelope-from jeff-ml@mountin.net) Received: (from daemon@localhost) by peak.mountin.net (8.9.1/8.9.1) id RAA16572; Sun, 20 Feb 2000 17:06:13 -0600 (CST) (envelope-from jeff-ml@mountin.net) Received: from dial-75.max1.wa.cyberlynk.net(207.227.118.75) by peak.mountin.net via smap (V1.3) id sma016567; Sun Feb 20 17:06:02 2000 Message-Id: <3.0.3.32.20000220170538.009084b0@207.227.119.2> X-Sender: jeff-ml@207.227.119.2 X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Sun, 20 Feb 2000 17:05:38 -0600 To: Kris Kennaway From: "Jeffrey J. Mountin" Subject: RE: openssl in -current Cc: current@FreeBSD.ORG In-Reply-To: References: <1D45ABC754FB1E4888E508992CE97E4F059CE6@teknos.teknos.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 10:17 PM 2/19/00 -0800, Kris Kennaway wrote: >This doesn't help. The RSA source not being there isn't the problem, the >problem is that there are two different binary versions depending on how >you build it (with rsaref or not). Source code builds aren't a problem, >they already work fine, it's people who install binary snapshots (e.g. >from the CD). As one that was bit by this, at a minimum we would need an errata entry, so that that want need RSA support will need to build the port and rebuild openssl on the base system, which requires both src/secure and src/crypto. While I don't have a problem with the cumbersome way of installing a fully function openssl, it does make more work for the ports guys, and so I'd vote to drop openssl from the base for the reason that the goal is a "good" point-oh release. Ports that depend on RSA should be made to check for the includes, which is the most obvious error when building. This being addressed. Just commenting. Considering that building and installing world takes quite a while, it would be nice to have a simple way, so wonder if a simple 'make all install' in secure/usr.bin/openssl will do it for everything that depends on openssl. Chapter 6.5 of the handbook implies that a make world is needed. Doesn't bother me (much), but might be considered cruel and unusual punishment to those not familiar with building. This whole deal is adding a lot of confusion. While many of us can work with/around these problems, it isn't really streamlined. My big question is - Do we really want to force a 'make world' on the those that want RSA support in openssl? That would be ugly, when before it was simply the matter of building only two ports. my .02 Jeff Mountin - jeff@mountin.net Systems/Network Administrator FreeBSD - the power to serve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message