From owner-freebsd-hackers Mon Apr 2 3: 9:19 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ringworld.nanolink.com (ringworld.nanolink.com [195.24.48.13]) by hub.freebsd.org (Postfix) with SMTP id 238EB37B71B for ; Mon, 2 Apr 2001 03:09:16 -0700 (PDT) (envelope-from roam@orbitel.bg) Received: (qmail 2199 invoked by uid 1000); 2 Apr 2001 10:08:07 -0000 Date: Mon, 2 Apr 2001 13:08:07 +0300 From: Peter Pentchev To: Max Khon Cc: hackers@freebsd.org Subject: Re: openssl/mdX.h and mdX.h name clashes Message-ID: <20010402130807.L462@ringworld.oblivion.bg> Mail-Followup-To: Max Khon , hackers@freebsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from fjoe@newst.net on Mon, Apr 02, 2001 at 05:03:20PM +0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Apr 02, 2001 at 05:03:20PM +0700, Max Khon wrote: > hi, there! > > /usr/include/mdX.h and /usr/include/openssl/mdX.h > both declare structures and functions with the same name > (structures are a bit different) and this is a bit troublesome for > applications that want to link with both -lmd and -lcrypto > > can we consider merging our mdX.h enhancements (MD5End, MD5File) to > openssl and switching to openssl/mdX.h entirely? I believe that this is the way things are supposed to happen; this has been discussed on -arch recently, although somebody stated that OpenSSL already has all the functionality. I wasn't quite able to find analogous functions in the source; and a single function, without setting up a BIO object and stuff, when all you need is the MD5 hash of a file by name, is definitely something useful. G'luck, Peter -- If this sentence were in Chinese, it would say something else. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message