On 22-09-2011 17:34, Dr. Stephen Henson wrote:
...
> exptag 6
> ptag 16
> Error reading S/MIME message...
>
Well it is expecting an OID but is getting a SEQUENCE.
Looking at your ASN1 dump perhaps the OID otherRevInfoFormat isn't present?
> ...
> OtherRevocationInfoFormat ::= SEQUENCE
On Thu, Sep 22, 2011, Gabriel Marques wrote:
> Thanks Steve and Erwann,
>
> Putting the OCSP response inside a tagged object did the job for
> OpenSSL recognizing the OtherRevocationInfoFormat.
> BouncyCastle also changed the CMS version to 5 automatically when I
> did it, and I've changed the OI
Thanks Steve and Erwann,
Putting the OCSP response inside a tagged object did the job for OpenSSL
recognizing the OtherRevocationInfoFormat.
BouncyCastle also changed the CMS version to 5 automatically when I did
it, and I've changed the OID to the proper one (id-ri-ocsp-response).
Now OpenSS
Le 22/09/2011 16:10, Dr. Stephen Henson a écrit :
On Thu, Sep 22, 2011, Erwann Abalea wrote:
[...]
In your examples, you set version to 3.
Based on your parsed example, it seems you correctly set the tag
([1]) for the "crls" element, but you didn't use the good encoding
for the "other" field (
On Thu, Sep 22, 2011, Erwann Abalea wrote:
> Le 21/09/2011 21:20, Gabriel Marques a écrit :
> >I'm developing a tool for signing digital TV apps, and one of the
> >goals was to embed OCSP responses into the CMS signature file of
> >the application.
> >The idea is that the broadcaster equipment wou
Le 21/09/2011 21:20, Gabriel Marques a écrit :
I'm developing a tool for signing digital TV apps, and one of the
goals was to embed OCSP responses into the CMS signature file of the
application.
The idea is that the broadcaster equipment would query the OCSP and
update the response with certain
