From owner-freebsd-stable Fri Apr 7 16:23:54 2000 Delivered-To: freebsd-stable@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 331F837C286; Fri, 7 Apr 2000 16:23:51 -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 QAA08051; Fri, 7 Apr 2000 16:23:50 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Fri, 7 Apr 2000 16:23:50 -0700 (PDT) From: Kris Kennaway To: Mikhail Teterin Cc: "Sean O'Connell" , stable@freebsd.org Subject: Re: openssl broken in 4.0? In-Reply-To: <200004072203.SAA01371@mail.virtual-estates.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 Fri, 7 Apr 2000, Mikhail Teterin wrote: > Well, I can still successfully use fetchmail linked against the port's > openssl to retrieve e-mail from this same server on one of my machines. Do me a favour and run: nm /usr/local/lib/libcrypto.a | grep RSA_eay_public_encrypt If it returns anything then you built the non-US version of OpenSSL which explains why the port behaves differently. > So, if this is not some new limitation that the bundled openssl has > versus the openssl installed by port, it is not the source of my trouble > :( There shouldn't be any functional differences, of course modulo bugs. 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