Re: pkcs#7 envelopeddata decoding

2006-08-19 Thread Michiel van Meersbergen
> I did try to decode the structure using the CMS routines, but they > also give me the exact same garbled output... > Not a signeddata structure as I would have expected, but the same > output never the less... So I expect this is a lower level problem > (not > the API used), I just can't find out

Re: pkcs#7 envelopeddata decoding

2006-08-16 Thread Michiel van Meersbergen
Nelson B wrote: >Michiel > >The old SEC_PKCS7 API is deprecated. It conforms to the original PKCS#7, >not to the newer "Cryptographic Message Syntax" RFC which superseded PKSC#7 >and is a superset of PKCS#7. > >NSS has a newer library that implements the newer RFC. IMO, all new >development shou

Re: pkcs#7 envelopeddata decoding

2006-08-15 Thread Nelson B
Michiel The old SEC_PKCS7 API is deprecated. It conforms to the original PKCS#7, not to the newer "Cryptographic Message Syntax" RFC which superseded PKSC#7 and is a superset of PKCS#7. NSS has a newer library that implements the newer RFC. IMO, all new development should be using it instead of

Re: pkcs#7 envelopeddata decoding

2006-08-15 Thread Michiel van Meersbergen
>Hmmm S/MIME uses DES3_CBC as: >1.2.840.113549.2.7 I wonder what is different between ANSI-X9.42 and S/MIME? I don't know. Any ideas how I can find out? I tried an internet search, but unsuccessfully up to now. >> Now NSS does recognize the encryption algorithm used, but i get some >> unexplai

Re: pkcs#7 envelopeddata decoding

2006-08-14 Thread Nelson B
Michiel van Meersbergen wrote: > Another 'oddity' I should mention, is that the PKCS#11 DLL which provides > access to the appropriate certificates and keys will ask for the proper > authentication itself - in other words, when a private-key function like > 'decrypt', 'sign' or 'unwrap' is called,

Re: pkcs#7 envelopeddata decoding

2006-08-14 Thread Bob Relyea
Michiel van Meersbergen wrote: Hello list, I'm running into some trouble with the SEC_PKCS7DecodeItem function. The input for this function is a PKCS#7 EnvelopedData object, which contains just one recipient, a session key (encrypted with the recipients' public key) and the encrypted content

pkcs#7 envelopeddata decoding

2006-08-14 Thread Michiel van Meersbergen
Hello list, I'm running into some trouble with the SEC_PKCS7DecodeItem function. The input for this function is a PKCS#7 EnvelopedData object, which contains just one recipient, a session key (encrypted with the recipients' public key) and the encrypted contents, encrypted with the above m