[xmlsec] bugfixes for mscrypto support

Mon, 15 Sep 2003 12:28:22 -0700

This is a multi-part message in MIME format.
--------------030103070801080400030007
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

>Yeah, you're right, pkcs12 is supported, but the phaos encryption test
>suite doesn't contain pkcs12 files, only plain private key files. So
>what we could do is create pkcs12 file with the correct certs/keys in
>there, but we'd have to create 'dummy' certificates for this, and
>somehow we'd have to create the pkcs 12 files, but probably with OpenSSL
>we could do this. Or we can create code that imports the private key, as
>it is defined in the original phaos file, with that information I think
>it is possible to import the private key into MS Crypto API, but then
>this code would be implemented solely for this particular purpose: The
>phaos test suite ... What do you think? (PS Sorry I keep on nagging
>about these tests)
>  
>

I guess pkcs#12 files with dummy certs is good option. BTW, does 
MSCrypto support pkcs#8
format?

>>Done. The patch applied and commited. However, after applying 
>>that patch I could not execute tests with mscrypto anymore because 
>>the test suite freezes on the first DSig test. I have not investigated 
>>the issue yet but it seems strange because the patch does not look
>>dangerous.
>>    
>>
>
>Hmmm, strange indeed. I've done a fresh checkout and didn't encounter
>any problems. So that is not helping you at all :(
>  
>
Yes. I was kicked out from Windows box by my kid and his "Sesame Street 
Games" last night :)
But I hope to research this problem tonight.

Aleksey

--------------030103070801080400030007
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1">
  <title></title>
</head>
<body text="#000000" bgcolor="#ffffff">
<br>
<blockquote type="cite" cite="mid000201c37bbd$e9a78090$0401a8c0@hert">
  <pre wrap="">Yeah, you're right, pkcs12 is supported, but the phaos encryption test
suite doesn't contain pkcs12 files, only plain private key files. So
what we could do is create pkcs12 file with the correct certs/keys in
there, but we'd have to create 'dummy' certificates for this, and
somehow we'd have to create the pkcs 12 files, but probably with OpenSSL
we could do this. Or we can create code that imports the private key, as
it is defined in the original phaos file, with that information I think
it is possible to import the private key into MS Crypto API, but then
this code would be implemented solely for this particular purpose: The
phaos test suite ... What do you think? (PS Sorry I keep on nagging
about these tests)
  </pre>
</blockquote>
<br>
I guess pkcs#12 files with dummy certs is good option. BTW, does
MSCrypto support pkcs#8<br>
format? <br>
<br>
<br>
<blockquote type="cite" cite="mid000201c37bbd$e9a78090$0401a8c0@hert">
  <blockquote type="cite">
    <pre wrap="">Done. The patch applied and commited. However, after applying 
that patch I could not execute tests with mscrypto anymore because 
the test suite freezes on the first DSig test. I have not investigated 
the issue yet but it seems strange because the patch does not look
dangerous.
    </pre>
  </blockquote>
  <pre wrap=""><!---->
Hmmm, strange indeed. I've done a fresh checkout and didn't encounter
any problems. So that is not helping you at all :(
  </pre>
</blockquote>
Yes. I was kicked out from Windows box by my kid and his "Sesame Street
Games" last night :)<br>
But I hope to research this problem tonight.<br>
<br>
Aleksey<br>
<br>
<br>
<br>
</body>
</html>

--------------030103070801080400030007--