[xmlsec] xmlsec-mscrypto code review (patch #5) and todo list
jan-olof.andersson at blcc.biz
Wed Sep 24 08:46:08 PDT 2003
when I define the xpath as a /../../ standard, what tag is it be looking for
in order to work properly?
From: xmlsec-admin at aleksey.com [mailto:xmlsec-admin at aleksey.com]On
Behalf Of Aleksey Sanin
Sent: den 24 september 2003 01:29
Cc: xmlsec at aleksey.com
Subject: Re: [xmlsec] xmlsec-mscrypto code review (patch #5) and todo
Never mind. Sorry, I did not read your message carefully :( I have tried
and it did not work for openssl (returned error) and crashed nss which
than the file we had before :)
Anyway, I did the same conversion myself. The new file seems to be working
fine on Linux (openssl/nss). And I could not test it on Windows because
getting "Keyset does not exist" error for every "CryptoAquireContext" call.
No idea why did this happen at all or when it'll be back to normal.
I have attached the file (gzipped). Can you try it with xmlsec-mscrypto,
Aleksey Sanin wrote:
> This would cause problems for NSS because it does not understand PEM
> Can you try to convert this PEM file back to DER and try the result,
> Wouter wrote:
>> B) Failing tests:
>> - merlin-xmldsig-twenty-three/signature-keyname
>> Something about loading some dll, looks like a problem with
>> my "cursed" box and don't worry about it too much.
>> I've converted the lugh.pem file into lugh.der, and replaced the
>> original lugh.der. Now the test is working. The original lugh.der I
>> couldn't recognize as anything (der encoded) valid. I've attached the
>> new lugh.der cert, so if no objections exist, it can replace the wrong
>> original lugh.der.
> xmlsec mailing list
> xmlsec at aleksey.com
More information about the xmlsec