[xmlsec] solve unload openssl problems

[J Gsealy]

________________________________
发件人: J Gsealy <jiaojingwei1001 at hotmail.com>
发送时间: 2018年7月27日 7:43
收件人: Aleksey Sanin
主题: 答复: [xmlsec] solve unload openssl problems

Hi Aleksey,
The path is correct，all the xmlsec1-openssl library are build in /usr/local/bin/
when I use xmlsec1.2.26 to make & install, there are have no error, and demo runs normally.
So I think other dependcies don't affect this.

The xmlsec1-openssl path:
[root at bogon ~]# find /usr/local/lib/ -name "libxmlsec1-openssl*"
/usr/local/lib/libxmlsec1-openssl.so.1.2.26
/usr/local/lib/libxmlsec1-openssl.so.1
/usr/local/lib/libxmlsec1-openssl.so
/usr/local/lib/libxmlsec1-openssl.la
/usr/local/lib/libxmlsec1-openssl.a

Dependcies path:
And openssl 1.1.0 compile to /usr/local/lib/ path
libxml2 and libxslt compile to /usr/lib64/ path

no error operation:
1.compile own openssl library
2.compile xmlsec1.2.26 release version
3.test sign1.c example:xmlsec1 --sign --privkey-pem rsakey.pem sign1-tmpl.xml > xmlsec.xml

have error operation:
1.compile my own openssl library
2.compile xmlsec-gm(have modified)
3.test sign1.c example:xmlsec1 --sign --privkey-pem rsakey.pem sign1-tmpl.xml > xmlsec.xml

So that, All compile passed. But mine xmlsec1 was ocurr error. and all library can be find in defalut path.

And I have another question,
If I want to add new algorithm, which file should I modified? I think there have some wrong in evp.c or
other files? Because I just changed this.

Thanks,
Gsealy

________________________________
发件人: Aleksey Sanin <aleksey at aleksey.com>
发送时间: 2018年7月26日 17:19
收件人: J Gsealy; xmlsec at aleksey.com
主题: Re: [xmlsec] solve unload openssl problems

Make sure that the xmlsec1-openssl library and other dependencies
can be found.

Aleksey

On 7/25/18 7:29 PM, J Gsealy wrote:
> Hi all:
>
>        I want to add new algorithm to xmlsec (EC algorithm with new
> curve, and new digest algorithm),
>
> the openssl have modified yet, and use normally.But when I add algorithm
> to xmlsec, and add new
>
> element <ECKeyValue> and <PublicKey>. I have modified include file
> <app.h>, <private.h>, <string.h>,
>
> <openssl/crypto.h>, <openssl/symbols.h>. And C file app.c, dl.c,
> string.c, openssl/crypto.c, openssl/signature.c .
>
> Compile can pass, but can’t load “xmlsec1-openssl”.
>
> There are error info:
>
> ------------------------------------------------------------------------
>
> loading "library openssl"...
>
> name:openssl, filename:libxmlsec1-openssl,
> function:xmlSecCryptoGetFunctions_openssl....
>
> func=xmlSecCryptoDLLibraryCreate:file=dl.c:line=138:obj=unknown:subj=lt_dlopenext:error=7:io
> function failed:name="libxmlsec1-openssl"; errno=2
>
> func=xmlSecCryptoDLGetLibraryFunctions:file=dl.c:line=444:obj=unknown:subj=xmlSecCryptoDLLibraryCreate:error=1:xmlsec
> library function failed:crypto=openssl
>
> func=xmlSecCryptoDLLoadLibrary:file=dl.c:line=401:obj=unknown:subj=xmlSecCryptoDLGetLibraryFunctions:error=1:xmlsec
> library function failed:
>
> Error: unable to load xmlsec-openssl library. Make sure that you have
>
> this it installed, check shared libraries path (LD_LIBRARY_PATH)
>
> envornment variable or use "--crypto" option to specify different
>
> crypto engine.
>
> Error: initialization failed
>
> func=xmlSecCryptoShutdown:file=app.c:line=71:obj=unknown:subj=unknown:error=9:feature
> is not implemented:details=cryptoShutdown
>
> Error: xmlSecCryptoShutdown failed
>
> Error: xmlsec crypto shutdown failed.
>
> ------------------------------------------------------------------------
>
> Which area should I change?
>
>
>
> Thanks.
>
>
>
> Gsealy
>
>
>
> _______________________________________________
> xmlsec mailing list
> xmlsec at aleksey.com
> https://nam02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.aleksey.com%2Fmailman%2Flistinfo%2Fxmlsec&data=02%7C01%7C%7C99bacbb856054bb6537708d5f31bf34d%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636682223723558195&sdata=REo%2BAcJ8yO0q1c7jSCrmzRRMpIsKJs00hOusXjCWpXw%3D&reserved=0
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.aleksey.com/pipermail/xmlsec/attachments/20180730/1d2ab269/attachment.html>