CAPICOM enveloped data interop question
From: Joe Kaplan \(MVP - ADSI\) (joseph.e.kaplan_at_removethis.accenture.com)
Date: 03/25/04
- Next message: Ken Schaefer: "Re: Windows Auth -- double hop issue??"
- Previous message: Raja: "? - Database Query & Saving to Application Cache"
- Next in thread: Michel Gallant: "Re: CAPICOM enveloped data interop question"
- Reply: Michel Gallant: "Re: CAPICOM enveloped data interop question"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Thu, 25 Mar 2004 15:51:54 -0600
Hi all,
I'm building an application that will create files to be exchanged with a vendor. The design specifies that the data in the files must be encrypted via RSA with a vendor-supplied certificate and signed with a trusted certificate provided by me. Files use standard PKCS#7 enveloped data to accomplish this. We'll use 3DES for the symmetric algorithm, so the details are in place.
Given that .NET doesn't have much if any support for enveloped data in System.Security.Cryptography, I thought I would be most productive using CAPICOM via interop to generate the enveloped data. However, I noticed this from MSDN documentation
which indicates that CAPICOM creates non-standard enrypteddata files that can only be read with CAPICOM. I need standard PKCS#7. My question is, does the restriction above apply to enveloped data that is encrypted AND signed, or just encrypted data? I'm still a novice with crypto and the distinctions to me are not clear.
Any help would be greatly appreciated.
Thanks!
Joe K.
- Next message: Ken Schaefer: "Re: Windows Auth -- double hop issue??"
- Previous message: Raja: "? - Database Query & Saving to Application Cache"
- Next in thread: Michel Gallant: "Re: CAPICOM enveloped data interop question"
- Reply: Michel Gallant: "Re: CAPICOM enveloped data interop question"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|