Hi,

thanks for your infos

can you please tell me, where I can find your postings to this topic, you made in the past?

On 19.03.2013 20:07, Jakob Bohm wrote:
Won't work (as you saw), this function doesn't take the actual ContentInfo structure as input, but data which it will (mis)treat
as an e-mail and then wrap in its own ContentInfo.  Notice how the
messageDigest in your result is not the one in the result from the
original RSADSI/VeriSign/Thawte/Symantec server.

When the input specifies a content type of "data", you could use
the bytes inside the inner OCTET STRING as input to cms like this
   openssl cms -sign -binary -content filewithrawdata.bin -outform DER
how should this work, because when calling openssl like this expects input from stdin ...
to get something close to the right response, but this won't work
if the request specifies a different content type.

I think there was a SourceForge project related to this
   (http://sf.net/projects/osslsigncode/)
But I don't know its status.

this is a good project, but I already have signcode.exe / signtool.exe;
I want to create the timestamp server part ..., using OpenSSL

I havn't used the OpenSSL source before ...

Thanks for any help,
Walter


Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to