[Lasso-devel] Problem when loading Lasso on RedHat 64bits

[Benjamin Dauvergne]

Clément OUDOT écrivait:
> Hello,
> 
> I installed Lasso and the Perl binding with RPMs from cyrus repo (RHEL
> 5.3 64 bits). I Imported metadata from ADFS, and at metadata load by
> Lasso I have this error :
> 
> (process:5528): Lasso-CRITICAL **: 2011-12-15 16:37:46 (lasso.c/:169)
> Unable to load default xmlsec-crypto library. Make surethat you have
> it installed and check shared libraries path(LD_LIBRARY_PATH)
> environment variable.

This message means that dynamic loading at *runtime* (really dynamic 
i.e.  after the main() function is started) of the crypto part of 
libxmlsec1 failed.

> (process:5528): lasso-CRITICAL **: lasso_provider_load_public_key:
> assertion `LASSO_IS_PROVIDER(provider)' failed
> 
> (process:5528): lasso-CRITICAL **: lasso_provider_load_public_key:
> assertion `LASSO_IS_PROVIDER(provider)' failed
> [Thu Dec 15 16:37:46 2011] [error] Unable to create Lasso server
> 
> 
> 
> I installed all dependencies, and when I check linked libraries on
> Lasso, all seems ok :
> 
> [root at VINFSSOF-04 lemonldap-ng]# ldd
>         libxmlsec1-openssl.so.1 => /usr/lib64/libxmlsec1-openssl.so.1
> (0x00002ac6e7f01000)

There we see that libxmlsec1-openssl is already dynamically linked at 
*load* time. I seems that your lasso library was not compiled in the 
same environment as the distribution you are running.

Could you give the content of the pkgconfig file 
/usr/lib/pkgconfig/xmlsec1.pc ?

Here on debian I have:

Cflags: -DXMLSEC_CRYPTO=openssl -D__XMLSEC_FUNCTION__=__FUNCTION__ 
-DXMLSEC_NO_GOST=1 -DXMLSEC_NO_XKMS=1 
-DXMLSEC_NO_CRYPTO_DYNAMIC_LOADING=1 -I${prefix}/include/xmlsec1     
-DXMLSEC_OPENSSL_098=1 -DXMLSEC_CRYPTO_OPENSSL=1

-DXMLSEC_NO_CRYPTO_DYNAMIC_LOADING means that dynamic loading is done at 
load time, I would not be surprised that this is also the case with 
Fedeora but not on RHEL 5.3.

-- 
"Java is a DSL for taking large XML files and converting them to stack traces"