Hi,
The certificate is well formed because i can open it in windows 2000.
I have this code :
string cert="certificate.der";
OpenSSLCryptoX509* x509 = NULL;
if (!cert.empty())
{
x509 = new OpenSSLCryptoX509();
ifstream s(cert.c_str());
string buf;
Scott Cantor a écrit :
For example, in the destructor of DSIGSignature, we have : delete[]
mp_ecPrefixNS;
It generates a bug .
Just curious, what did it do?
I think
it is a memory overwrite.
Thinks for your answer. I had replace all delete[]
with XMLString::release.
> For example, in the destructor of DSIGSignature, we have : delete[]
> mp_ecPrefixNS;
> It generates a bug .
Just curious, what did it do?
> if i replace with the code : XMLString::release(&mp_ecPrefixNS);
> i haven't got the problem.
>
> Have you got an idea ? did i have bad compilation
Hi,
I use VC 7 (.NET), OpenSSL 0.9.7c and Xerces-c 2.3.0
And i have compiled the Xml Security library without Xalan.
First i have compiled the samples. It was Ok.
But when i wanted to run it, i had a bug. The release of XMLCh does work.
For example, in the destructor of DSIGSignature, we have :
Berin,
Just trying to think through 5D002 - would it not be the case that part
of the signature code is more under EAR, or perhaps is the generic EAR99,
or just under 5D002.a ?
Though I guess we need to apply an ECCN to the -whole- distribution; so
that would atomatically be a 5D002, in the intr
