RE: building c++ xsec1.1

2005-03-18 Thread harish suvarna
I did build xalan1.7 but of no use. I keep getting the link errors. I removed the comment for #define XSEC_NO_XALAN . Then it could buid fine. -Harish Jesse Pelton <[EMAIL PROTECTED]> wrote: Sorry, I shouldn't have said you need to build Xalan, just that you need to have it (libraries and header

XML-Security-C with OpenSSL overly strict about base64 line lengths

2005-03-18 Thread Jesse Pelton
OpenSSLCryptoKeyRSA::verifySHA1PKCS1Base64Signature() uses OpenSSL's EVP_Decode...() routines to decode the base64 contents of SignatureValue. This fails if line breaks don't occur where OpenSSL thinks they should. I think this is contrary to the specification (see rationale below), and that this

RE: building c++ xsec1.1

2005-03-18 Thread Jesse Pelton
Sorry, I shouldn't have said you need to build Xalan, just that you need to have it (libraries and headers) to use XPath. Xerces is a requirement to use XSec at all, but again, you should be able to use prebuilt binaries. From: harish suvarna [mailto:[EMAIL PROTECTED] Sent: Friday

RE: building c++ xsec1.1

2005-03-18 Thread harish suvarna
Thank you Jesse for the help. I downloaded the xalan1.7 from an archive of apache. It already had the built executables and libs. I am using them. I did not build xalan. But the source and project files are there. But the project files are based on VC6. I will build in VC++7 and see. Initially I s

RE: building c++ xsec1.1

2005-03-18 Thread Jesse Pelton
Did you build and link Xalan or define XSEC_NO_XALAN in XSEC32Config.hpp? You'll need to build Xalan if you require XPath support, otherwise you can tell XSec to build without it. From: harish suvarna [mailto:[EMAIL PROTECTED] Sent: Thursday, March 17, 2005 7:32 PMTo: security-d