I'm trying to produce nested structures, like signed-enveloped-signed data.
This is explicitly described in the various RFCs, but I can't figure out how to
get OpenSSL to produce valid output, and I can't find any code examples of
doing this.
What I'm doing (which doesn't quite work) is this: f
Hello,
> Am 22.11.2016 um 23:25 schrieb Dr. Stephen Henson :
>
> On Tue, Nov 22, 2016, Harald Koch wrote:
>
>> Hello,
>>
>> I???m facing a critical situation in my application when creating a signed
>> SMIME message using SHA1 as message digest algorithm. In openSSL 1.0.2 (i.e.
>> 1.0.2h), th
On Tue, Nov 22, 2016, Harald Koch wrote:
> Hello,
>
> I???m facing a critical situation in my application when creating a signed
> SMIME message using SHA1 as message digest algorithm. In openSSL 1.0.2 (i.e.
> 1.0.2h), the following command worked as expected:
>
> /opt/openssl-1.0.2h/bin/opens
Yes. The build methods were kept constant at first as I tried to upgrade.
Currently I am using STANDARDSDK_500 to build for CE50_ARMV4I, or at least that
is the build target that was tested. We also build for many other target
platforms as well, I haven't tested any of them yet. Details coul
Hi All.
I wish to compile openssl libraries for a STM32-processor (which would then
be linked statically with our application-framework code).
Now. I believe that OpenSSL uses tonnes of "malloc"s and "free"s. But for
bare-metal-systems (without any formal OSes), we generally don't have any
heap-
Hello,
I’m facing a critical situation in my application when creating a signed SMIME
message using SHA1 as message digest algorithm. In openSSL 1.0.2 (i.e. 1.0.2h),
the following command worked as expected:
/opt/openssl-1.0.2h/bin/openssl smime -sign -in original_message -signer
cert_key.pem
