Date: Fri, 25 Feb 2000 17:39:31 +0800 From: Peter Wemm <peter@netplex.com.au> To: "Jordan K. Hubbard" <jkh@zippy.cdrom.com> Cc: Kris Kennaway <kris@FreeBSD.org>, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/secure/usr.bin/openssl Makefile src/secure/usr.bin/scp Makefile src/secure/usr.bin/ssh Makefile src/secure/usr.bin/ssh-add Makefile src/secure/usr.bin/ssh-agent Makefile src/secure/usr.bin/ssh-keygen Makefile ... Message-ID: <20000225093931.D9C761CD7@overcee.netplex.com.au> In-Reply-To: Message from "Jordan K. Hubbard" <jkh@zippy.cdrom.com> of "Fri, 25 Feb 2000 01:30:49 PST." <93705.951471049@zippy.cdrom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
"Jordan K. Hubbard" wrote: > > There is no reason for anyone !US to be using RSAREF, since it's inferior > > to the openssl native RSA implementation inside libcrypto. > > So you're saying there's a disparity between the libcrypto in the > international crypto repository and the one in the US, or that non-US > sites still need to wholesale replace this library? I thought getting > away from that was the whole point of abstracting rsaref away, if so. It's done. *everybody* is supposed to just use -lcrypto, regardless of whether they are in the US or elsewhere. -lrsaref and -lRSAglue should not be used in new stuff, unless 3.x portability is required. The only special case at present is if you are in the US and are trying to build static binaries using RSA. In that sole case, you need to add a reference to librsaref.a on the link line. Since we link ports dynamic by default, it shouldn't be an issue. Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000225093931.D9C761CD7>