It's fine for me. Personally I don't think that you really want to show
any detailed error message to the user. Signatures and encryption
is a backend stuff. Most errors are total failures and you could not
recover from them. For example, in the situation you mentioned
the error case is applicaton
To link libraries dynamically comment the following line in
apps/Makefile.am:
xmlsec_LDFLAGS = -static
(and do not forget to run ./autoconf.sh; ./configure after
this)
The xmlsec library already has two packages: RPM ans RPMS. Personally, I
do not
see advantages of having xmlsec and xmlsec
No luck. I uninstalled the original libxml (v1) rpm that was on the system, and it
produced the same result.
I pulled down the Mandrake version of libxml2 1.0.17 RPM, as well as compiled it from
xmlsoft.org, with the same result.
I downloaded and compiled the latest CVS snapshot of OpenSSL 0.
Looks like there is a problem on LibXML level. One of possible reasons is
library mismatch (xmlsec loads old/wrong version of LibXML2 libraries
when you are compiling it). I would suggest to do following:
1) ungzip/untar xmlsec-*.tar.gz into new folder
2) run the following commands and not
I have installed the xmlsec-0.0.5 source tree on my Mandrake 8.1 system. It appears
to compile fine, but it fails all the tests in the test suite with errors such as the
following:
validity warning: or: Error: failed to read XML file
"./merlin-xmldsig-twenty-three/signature-enveloped-dsa.xml
