Dear Michael,
> Am 29.10.2020 um 22:55 schrieb Michael Richardson :
>
>> Yes, the signed message is contained in a HTTP(S) multipart request
>> with more payload and header information, sure. The only different part
>> is the signed content, all other content has been manually checked,
>> they ar
Harald Koch wrote:
>> Am 29.10.2020 um 14:12 schrieb Michael Richardson
>>> - "Unable to verify content integrity: Missing data"
>>> - "The system is unable to find out the sign algorithm of the inbound
message"
>>
>>> I digged a bit deeper into the ASN1 data („cat signature
Dear Michael,
> Am 29.10.2020 um 14:12 schrieb Michael Richardson
>> - "Unable to verify content integrity: Missing data"
>> - "The system is unable to find out the sign algorithm of the inbound
>> message"
>
>> I digged a bit deeper into the ASN1 data („cat signature.base64 | base64 -d
>> | o
Harald Koch wrote:
> my task is to sign a message in C for SMIME exchange, which works as
> expected and openSSL is self-fulfilling with itself in successful
> verification (and unsuccessful in produced errors as expected). I've
> tested PKCS7 SMIME functions, as well as CMS ones,
Hello,
my task is to sign a message in C for SMIME exchange, which works as expected
and openSSL is self-fulfilling with itself in successful verification (and
unsuccessful in produced errors as expected). I've tested PKCS7 SMIME
functions, as well as CMS ones, leading to the same result: the r
