Re: [PATCH] use libcrypto routines in gnulib

2013-12-08 Thread Pádraig Brady
On 12/09/2013 01:40 AM, Paul Eggert wrote: > Pádraig Brady wrote: >> Where would be best to initialize this? > > Maybe m4_divert_once([DEFAULTS], [LIB_CRYPTO=])? I'll try it out. >> The libgcrypt replacement calling out to libcrypto seems to work. >> tests pass anyway. > > I assume you're prep

Re: [PATCH] use libcrypto routines in gnulib

2013-12-08 Thread Paul Eggert
Pádraig Brady wrote: > Where would be best to initialize this? Maybe m4_divert_once([DEFAULTS], [LIB_CRYPTO=])? > The libgcrypt replacement calling out to libcrypto seems to work. > tests pass anyway. I assume you're preparing a gnulib patch that would prefer libgcrypt to libcrypto, or somethin

Re: [PATCH] use libcrypto routines in gnulib

2013-12-08 Thread Pádraig Brady
On 12/09/2013 12:15 AM, Paul Eggert wrote: > Pádraig Brady wrote: >> * m4/gl-openssl.m4 (gl_CRYPTO_CHECK): Don't empty LIB_CRYPTO > > That would inherit LIB_CRYPTO from the environment, no? > It might be better to move the LIB_CRYPTO= into the > initialization code. Right, I was worried about tha

Re: [PATCH] use libcrypto routines in gnulib

2013-12-08 Thread Paul Eggert
Pádraig Brady wrote: > * m4/gl-openssl.m4 (gl_CRYPTO_CHECK): Don't empty LIB_CRYPTO That would inherit LIB_CRYPTO from the environment, no? It might be better to move the LIB_CRYPTO= into the initialization code. Also, is libgcrypt compatible with libcrypt with respect to MD5, SHA512, etc.?

Re: [PATCH] use libcrypto routines in gnulib

2013-12-08 Thread Pádraig Brady
On 12/03/2013 12:03 AM, Pádraig Brady wrote: > On 12/02/2013 10:48 PM, Paul Eggert wrote: >> On 12/02/2013 01:05 PM, Pádraig Brady wrote: >>> each project would have >>> to add LIB_CRYPTO_MD5 etc. to their list of libs similarly >>> to the coreutils patch I had inline in my previous mail. >> >> Tha

Re: [PATCH] md5, sha1, sha256, sha512: add 'auto', and a way to specify default

2013-12-08 Thread Pádraig Brady
On 12/08/2013 03:38 PM, Ludovic Courtès wrote: > Paul Eggert skribis: > >> I needed something like this for Emacs, and these changes should >> affect existing uses so I took the liberty of pushing them. > > BTW, wouldn’t it be a problem if OpenSSL got linked into Emacs? > > In general, it’s not

Re: [PATCH] md5, sha1, sha256, sha512: add 'auto', and a way to specify default

2013-12-08 Thread Paul Eggert
Ludovic Courtès wrote: > BTW, wouldn’t it be a problem if OpenSSL got linked into Emacs? I'm not aware of a problem, if OpenSSL is a library that is normally distributed with the major components of the operating system, but this topic has been raised on emacs-devel (see

Re: [PATCH] md5, sha1, sha256, sha512: add 'auto', and a way to specify default

2013-12-08 Thread Ludovic Courtès
Paul Eggert skribis: > I needed something like this for Emacs, and these changes should > affect existing uses so I took the liberty of pushing them. BTW, wouldn’t it be a problem if OpenSSL got linked into Emacs? In general, it’s not advisable to link OpenSSL into GPL’d programs AIUI, so I won

Re: [PATCH] md5sum, sha*sum: use libcrypto where available

2013-12-08 Thread Pádraig Brady
On 12/08/2013 07:45 AM, Paul Eggert wrote: > Pádraig Brady wrote: > >> If that was further adjusted to document the default, >> then we could adjust coreutils to using this mechanism. > > I pushed the following into gnulib to try to support that. > This is tested with GNU Emacs, but not with core