From owner-freebsd-stable Tue Feb 29 18: 9:53 2000 Delivered-To: freebsd-stable@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 60D2C37B76D; Tue, 29 Feb 2000 18:09:47 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 5E9872E8109; Tue, 29 Feb 2000 18:09:47 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Tue, 29 Feb 2000 18:09:47 -0800 (PST) From: Kris Kennaway To: Clifton Royston Cc: Matt Heckaman , Kenneth W Cochran , freebsd-stable@freebsd.org Subject: Re: Trouble installing xpdf port in 3.4-stable In-Reply-To: <20000229080637.F5108@lava.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 29 Feb 2000, Clifton Royston wrote: > My understanding is that it has to be provided as binary, not source, > which seems like kind of a show-stopper for open source OSes. Make > sense? I didn't think so. We're still waiting on a legal interpretation of the new regs from WC's lawyers..but it certainly seems like (subject to some procedural restrictions) we would be allowed to export crypto now. The "some restrictions" is the bit which needs to be clarified before we start doing it, to make sure no-one gets in trouble. > However... has anybody looked at the install procedure for OpenBSD > 2.6? It's really really slick. (Excuse me while I rave...) As part of Sounds like you're going to love FreeBSD 4.0, then, which does exactly this (OpenSSH is in the base system and enabled out of the box if you choose it, along with OpenSSL (strong crypto toolkit)). I think we've managed to do a better job of it than OpenBSD, too, at least under the hood (I haven't seen Jordan's sysinstall changes in action yet). Kris ---- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message