This is pretty easy to fix with a call to gcry_check_version() within
kmgrcy_init_algs().
I've attached a patch that should be a temporary fix for version 3.1.1.
I'm in the process of preparing an updated release (3.1.2), together with an
improved version 4.0.
RWP
+-- on Tue, Feb 24, 2009 at 04:19:39PM +0100, Agustin Martin wrote: ---+
> reassign 516922 cryptmount
> found 516922 3.1.1-1
> thanks
>
> On Tue, Feb 24, 2009 at 03:36:21PM +0100, Werner Koch wrote:
> > On Tue, 24 Feb 2009 15:09, agustin.mar...@hispalinux.es said:
> >
> > > Last libgcrypt11 seems to have added a problem regarding cryptmount.
> > > Since I
> >
> > Cryptmount does not properly initialize Libgcrypt. From the NEWS file:
> ...
> > Please fix Cryptmout.
>
> Thanks a lot for the really quick reply.
>
> Reassigning to cryptmount alone and setting found version.
>
> --
> Agustin
>
>
diff -Nuar cryptmount-3.1.1/armour-gcry.c cryptmount-3.1.1-patched/armour-gcry.c
--- cryptmount-3.1.1/armour-gcry.c 2008-10-03 12:39:16.000000000 +0100
+++ cryptmount-3.1.1-patched/armour-gcry.c 2009-02-24 20:18:34.000000000 +0000
@@ -384,7 +384,8 @@
static int kmgcry_init_algs()
{
- /* Nothing needed */
+ (void)gcry_check_version(NULL); /* Initializes library as side-effect */
+
return 0;
}
