Thank you very much for the reply and the code. It's exactly what I needed. There is a slight problem with calling sbStrToXMLCh() on the safeBuffer. In the WinCAPICryptoX509 constructor, the buffer type in the safeBuffer is never set, so it stays BUFFER_UNKNOWN, which causes the sbStrToXMLCh function to throw an exception. Changing the type to BUFFER_CHAR fixes the problem. As a certificate novice, I'm not sure what the correct behavior is. I will open a new thread to address it.By this do you mean embedding the certificate in the signature? If so, this sounds like it would work best for us. Do you have any sample code that does this?I wrap KeyInfo myself now, I don't use this library directly for that part, it's not as powerful as my code. My old code used it, you can look at:http://tinyurl.com/2pzlpp Look at the sign() method. -- Scott Thanks again for the help! Kelly |
- Standard for embedding KeyInfo Kelly Graus
- RE: Standard for embedding KeyInfo Scott Cantor
- Re: Standard for embedding KeyInfo Kelly Graus
- RE: Standard for embedding KeyInfo Scott Cantor
- Re: Standard for embedding KeyInfo Kelly Graus
- Re: Standard for embedding KeyInfo Arshad Noor