From owner-freebsd-questions Wed Apr 12 17: 4: 8 2000 Delivered-To: freebsd-questions@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id D96DD37BA87; Wed, 12 Apr 2000 17:04:05 -0700 (PDT) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id RAA98757; Wed, 12 Apr 2000 17:04:04 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Wed, 12 Apr 2000 17:04:04 -0700 (PDT) From: Kris Kennaway To: Doug Barton Cc: freebsd-questions@FreeBSD.org Subject: Re: OpenSSH problem in 3.4 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 12 Apr 2000, Doug Barton wrote: > > Are you linking explicitly against libRSAglue? You need to do this with > > the stock OpenSSL - our version does dlopen() magic to get around it. > > Linking against libRSAglue in the app gets me: > > /usr/local/lib/libRSAglue.a(rsaref.o): In function > `RSA_ref_private_decrypt': And these are all defined in librsaref To summarize, you need something like: -L/usr/local/lib -lcrypto -lRSAglue -lrsaref for FreeBSD 2.x or 3.x systems in the US (i.e. if you use the standard openssl port). (For 3.x systems outside the US, i.e. who don't use librsaref, the link line is "-L/usr/local/lib -lcrypto") For 4.x and 5.x you need -lcrypto regardless of whether or not you're using librsaref. 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-questions" in the body of the message