Date: Sat, 25 Jun 2005 18:42:08 -0600 (MDT) From: "M. Warner Losh" <imp@bsdimp.com> To: cperciva@freebsd.org Cc: cvs-src@freebsd.org, src-committers@freebsd.org, cvs-all@freebsd.org, mark@grondar.org Subject: Re: cvs commit: src/lib/libmd Makefile sha256.3 sha256.h sha256c.c shadriver.c src/sbin/md5 Makefile md5.c src/sys/sys param.h Message-ID: <20050625.184208.118628146.imp@bsdimp.com> In-Reply-To: <42BDB8B9.8020400@freebsd.org> References: <200506251958.j5PJwIhq054393@grunt.grondar.org> <42BDB8B9.8020400@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
In message: <42BDB8B9.8020400@freebsd.org>
Colin Percival <cperciva@freebsd.org> writes:
: Mark Murray wrote:
: > Colin Percival writes:
: >> MFC the addition of sha256 to libmd and md5(1).
: >
: > I still object to the use of "manufactured" 64-bit quantities
: > instead of using uint64_t, and less strongly to the re-engineering
: > of endianness code when we already have functional library routines
: > to do the job.
:
: Changing that is on my TODO list, but several people were asking me to
: MFC sha256, so I decided to do the MFC now and then MFC other changes
: later.
BTW, I'd like to bring in the OpenBSD md5.c driver program. Any
objections to doing that if I make sure it connects the sha256 stuff
you've added that I'm not sure is in the OpenBSD one.... This is
primarily to clear up any confusion that surrounds the md5.c file...
Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050625.184208.118628146.imp>