From owner-freebsd-current@FreeBSD.ORG Sun Apr 11 06:58:57 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ABF5E16A4CE for ; Sun, 11 Apr 2004 06:58:57 -0700 (PDT) Received: from mail.atlasbook.com (particle-pat.atlasbook.com [66.161.22.37]) by mx1.FreeBSD.org (Postfix) with ESMTP id 944AB43D39 for ; Sun, 11 Apr 2004 06:58:57 -0700 (PDT) (envelope-from dd@freebsd.org) Received: from ajax.nimone.com (unknown [192.168.168.100]) by mail.atlasbook.com (Postfix) with ESMTP id 509F551; Sun, 11 Apr 2004 13:58:57 +0000 (UTC) Received: (from dima@localhost) by ajax.nimone.com (8.11.6+Sun/8.10.2) id i3BDwqw15904; Sun, 11 Apr 2004 13:58:52 GMT X-Authentication-Warning: ajax.nimone.com: dima set sender to dd@freebsd.org using -f Date: Sun, 11 Apr 2004 13:58:52 +0000 From: Dima Dorfman To: Kaarthik Sivakumar Message-ID: <20040411135851.GC15793@trit.org> References: <200404080744.i387ie0w047939@grimreaper.grondar.org> <86n05m3a31.fsf@comcast.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <86n05m3a31.fsf@comcast.net> User-Agent: Mutt/1.4i X-PGP-Key: 69FAE582 (http://www.trit.org/~dima/dima.asc) X-PGP-Fingerprint: B340 8338 7DA3 4D61 7632 098E 0730 055B 69FA E582 cc: current@freebsd.org cc: Mark Murray Subject: Re: libmp and libcrypto X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Apr 2004 13:58:57 -0000 Kaarthik Sivakumar wrote: > MM> Confirmed. Our libmp is a wrapper round the BIGNUM functions in > MM> libcrypto. > > I read the man page for libmp (right after sending this mail) and it > says that we should move to using BIGNUM in libcrypto directly. Is > there a document of some sort that shows how to move things over? At > this time, it looks like FreeBSD is the only OS that recommends using > something other than (g)mp for BIGNUM support. I don't think anyone still recommends using the antiquated (and largely broken) Berkeley mp(3) interface; it's only provided for compatibiltiy with applications that haven't been ported to use something more modern. libgmp and the OpenSSL BIGNUM interface are more modern, and either one is fine. If you have an application that wants gmp, just install the libgmp4 port. Dima.