On Thu, May 31, 2001 at 12:14:02AM -0400, Cliff Woolley wrote: > On 31 May 2001 [EMAIL PROTECTED] wrote: > > > @@ -65,6 +65,8 @@ > > * add apr_crypt() and APR_HAS_CRYPT for apps to determine whether the > > crypt() function is available, and a way to call it (whether it is > > located in libc, libcrypt, or libufc) > > + Justin says: Should apr_crypt() be in apr-util? > > + > > Status: Greg +1 (volunteers) > > >From the description, it sounds to me like apr_crypt is a portability > wrapper, not a function that is inherently portable like all the things in > apr-util. Therefore it belongs in APR itself IMO...
Well, I was thinking of the crypto dir in apr-util. sha1 is already there. md5 would make sense there - I think we've agreed that if we *can* replace md5 in uuid, it makes sense to place md5 in apr-util. The only reason that md5 is in APR is because we don't always have random data sources. Sander has submitted a patch for md4 (I'm slowly working my way through patches...). I think that wherever these other crypto functions go, so should crypt(). But, as always, I'm open to discussion on this. Granted, crypt() is slightly different than the other crypto algorithms as my systems have it as a standard library call. But, not all systems will have it. -- justin
