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,
Hi, There,
I am new to openSSL and currently working on integrating openSSL libraries in
our product which has linux-ppc platform. We have an old version of kernel in
our product i.e. 2.6.37.6. I want to integrate lighttpd with openSSL for HTTPS
support. When I use openSSL-1.1.1b or older versi
On 29/10/2020 03:52, Thomas Antonio via openssl-users wrote:
> Hello, how does openSSL determine the Record Layer Version used to
> initiate a ClientHello message to the server? I believe the
> determination is made at this level.
>
> When testing using multiple implementations (Python Requests
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
