The CMS application only supports the econtent_type option for the sign
operation. The trivial patch below adds support for the encrypt operation
(enveloped-data).
This allows signalling of the content of enveloped-data structures.
Kind regards,
Paul
diff -u -r openssl-1.0.0d//apps/cms.c
About a week ago I submitted the report below.
Has any developer plans to look into this?
Kind regards,
Paul
-
I've tracked down the problem. It is in the RSA blinding code, because
RSA_blinding_off(rsa) after the RSA
I've tracked down the problem. It is in the RSA blinding code, because
RSA_blinding_off(rsa) after the RSA *rsa = RSA_new() solves the problem.
I cc't rt to create a ticket for this bug.
Paul
Original message:
--
I have
Does anybody know if (parts of) OpenSSL compile and run on the pSos
operating system?
In case it matters: I'm particularly interested in the crypto (algorithms,
x509, etc.) part of OpenSSL, which could (except BIO, ...?) be quite
portable I guess.
Regards,
Paul
Working on code to read/process and create x509 certificates I encountered
the following.
The following code results in an ASN1_TIME structure with internal length
field
of 14 (date1-length =14).
date1 = ASN1_TIME_new();
ASN1_GENERALIZEDTIME_set_string(date1, 20020819093712);
When
The following code results in an ASN1_TIME structure with internal
length
field
of 14 (date1-length =14).
date1 = ASN1_TIME_new();
ASN1_GENERALIZEDTIME_set_string(date1, 20020819093712);
When extracting time out an existing certificate however with this
date/time
would result
