Date: Fri, 16 May 2003 00:44:04 +0100 From: Mark Murray <mark@grondar.org> To: Dag-Erling Smorgrav <des@ofug.org> Cc: arch@freebsd.org Subject: Re: NOCRYPT / NOSECURE Message-ID: <200305152344.h4FNi4gN032787@grimreaper.grondar.org> In-Reply-To: Your message of "Thu, 15 May 2003 21:32:23 %2B0200." <xzpllx8hupk.fsf@flood.ping.uio.no>
next in thread | previous in thread | raw e-mail | index | archive | help
Dag-Erling Smorgrav writes: > Mark Murray <mark@grondar.org> writes: > > If openssl's des(1) is the same as our bdes(1) (ie, gives the same results) > > then I'm in support of this. > > I haven't compared OpenSSL'S des(1) directly with bdes(1), but they > are both ports (or reimplementations) of Sun's des(1), and I've used > OpenSSL's des(1) in the past to exchange data with Solaris users who > were using Sun's des(1). I've converted our bdes(1) to use the openSSL library. I've also done ed(1). :-). libcipher is now OBE. > > I'd also approve of a wrapper script that > > calls openssl(1) or des(1) and make a compatible bdes(1). > > That's possible of course, but bdes(1) has a lot of command-line > options which we'd need to implement. Probably not worth the trouble. No problem. See above :-). > > Similar scripts > > may be a good idea for md5(1) and sha1(1). > > 'ln -s /usr/bin/openssl /usr/bin/md5' is almost right for md5(1), > except for some parentheses in the output IIRC. ISTR the same goes > for sha1(1). A one-liner shell script does it :-). M -- Mark Murray iumop ap!sdn w,I idlaH
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200305152344.h4FNi4gN032787>