Date: Fri, 25 Feb 2000 18:04:07 +0800 From: Peter Wemm <peter@netplex.com.au> To: Kris Kennaway <kris@FreeBSD.org> Cc: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>, 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: <20000225100408.F41191CE4@overcee.netplex.com.au> In-Reply-To: Message from Kris Kennaway <kris@FreeBSD.org> of "Fri, 25 Feb 2000 01:50:47 PST." <Pine.BSF.4.21.0002250146390.57682-100000@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Kris Kennaway wrote: > On Fri, 25 Feb 2000, Peter Wemm wrote: > > > > 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 > > The issue is that the intl version of libcrypto is different from the US > version. That was never the issue we were addressing here..the issue was > making it so there weren't two versions of the *US* libcrypto. There aren't two versions from an application's perspective. It only has to use -lcrypto and it's all taken care of. That's regardless of whether it's a US or non-US libcrypto. The only time that the application must make special care is if it's trying to link statically. > > should not be used in new stuff, unless 3.x portability is required. > > Or you want it to link on another platform. I'm not sure at what point it > was decided that -lrsaref -lRSAglue became deprecated (as opposed to > optional) because they're required for cross-platform compatability (in > both directions). With the adjustments I've made, if you supply librsaref, it'll now work with -lcrypto -lRSAglue -lrsaref. It just won't use the last two as libRSAglue is a stub for application build compatability and librsaref won't be linked against by libcrypto, libcrypto will dlopen() librsaref itself. Cheers, -Peter 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?20000225100408.F41191CE4>