On 07/07/2016 20:08, Chris Bare wrote:
EVP_get_digestbyobj fails for ecdsa-with-SHA256
ecdsa-with-SHA256 is not a digest algorithm, it is a signature
algorithm with a specific choice of digest algorithm (SHA256).
In OpenSSL 1.0.2 and older there is a very old compatibility
feature which
Ok, that makes sense with what I'm seeing. I just tried changing this:
const EVP_MD* md = EVP_get_digestbyobj(sig_alg_oid);
to this:
const EVP_MD* md = EVP_get_digestbyname("SHA256");
and it all worked correctly.
so given that I have an OID for ecdsa-with-SHA256, is there a function that
EVP_get_digestbyobj fails for ecdsa-with-SHA256
I'm trying to perform a standard signature verification using the EVP_*
functions.
I think my code is correct, because it all runs fine if the digest is
RSA-SHA256.
I have an ASN1_OBJECT that specifics the signature/disgest type.
Here is my code
Am 07.07.16 um 00:16 schrieb Dr. Stephen Henson:
On Wed, Jul 06, 2016, Stephan M?hlstrasser wrote:
While doing research on this, we found one thing that looks
suspicious in the CMS objects generated by OpenSSL 1.0.2. When
dumping the CMS object with dumpasn1, the key wrap algorithm is
encoded
Am 06.07.16 um 23:35 schrieb Dr. Stephen Henson:
...
Yes, the other version cannot decrypt the CMS object generated by
OpenSSL. I did some tests with Bouncy Castle, and it also cannot
decrypt the CMS object.
What might be interesting is that on the other hand Windows
CryptoAPI is able to
On 06/07/16 16:55, Scott Neugroschl wrote:
> I’m building 1.0.1t with the no-srp option.When I do, I get
> thefollowing error
>
>
>
> making all in ssl...
>
> make[1]: Entering directory `/users/scottn/openssl-1.0.1t/ssl'
>
> make[1]: *** No rule to make target
Is there any good rule of thumb for when to use:
*-k * versus
*-K *
*
*
Also, what does the term IV refer to in reference to *-iv IV*?
Thanks in advance,
Warron
--
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
