[xmlsec] oracle / crypto issue
Aleksey Sanin
aleksey at aleksey.com
Thu Dec 2 13:57:52 PST 2010
The idea is that you can link against libclntst11.a directly instead of
openssl. This would work if you find out the exact openssl version used
by Oracle.
Aleksey
On 12/2/10 1:43 PM, Erik Smith wrote:
> I played around with that idea for a while, but since this is a
> "multiple definition" issue, I'm not sure how messing with the search
> paths helps.
> nm data:
> libcrypto.a: 00000000000019c0 T ERR_load_strings
> libclntst11.a: 0000000000000058 T ERR_load_strings
>
> erik
>
> On Thu, Dec 2, 2010 at 1:26 PM, Roumen Petrov <xmlsec at roumenpetrov.info
> <mailto:xmlsec at roumenpetrov.info>> wrote:
>
> Erik Smith wrote:
>
> I need to load certificate keys to validate XML containing XML
> Security
> content. openssl seems to be the path of least resistance, but
> there seems
> to be a static library conflict between Oracle's libclntst11.a
> file and
> symbols in libcrypto.a, presumably because Oracle statically
> links in a
> version of crypto. I get errrors like this:
>
> libclntst11.a(truntim.o): In function `ERR_load_strings':
> truntim.c:(text.unlikely+0x58): multiple definition of
> `ERR_load_strings'
> libcrypto.a(err.o):err.c:(.text+0x19c0): first defined here
> /usr/bin/ld: Warning: size of symbol `ERR_load_strings' changed
> from 97 in
> libcrypto.a(err.o) to 10 in libclntst11.a(truntim.o)
>
> Is there an easy way around this openssl / crypto conflict?
>
> gcrypt doesn't have this issue but it doesn't support
> certificate keys. Is
> there a preferred cryptographic library that provides a broad
> range of
> support with the least amount of issues?
>
> erik
>
>
> ./configure --help will show how to set header/library search paths.
> Put flags with paths to openssl headers and libraries so that
> compiler/linker to find them first.
>
> Roumen
>
>
>
>
> _______________________________________________
> xmlsec mailing list
> xmlsec at aleksey.com
> http://www.aleksey.com/mailman/listinfo/xmlsec
More information about the xmlsec
mailing list