Thanks everyone, your replies were most helpful.
On Sat, 2 Nov 2019 at 06:42, Jordan Brown
wrote:
> On 10/31/2019 7:35 AM, Viktor Dukhovni wrote:
>
> My advice would be to avoid specific support for any *particular* digest
> algorithm. Instead, provide bindings to:
>
> -
On 10/31/2019 7:35 AM, Viktor Dukhovni wrote:
> My advice would be to avoid specific support for any *particular*
> digest algorithm. Instead, provide bindings to:
> - EVP_get_digestbyname(),
> - EVP_MD_CTX_create(3),
> - EVP_DigestInit_ex(3),
> - EVP_DigestUpdate(3),
> -
On 31/10/2019 11:59, Samuel Williams wrote:
> I am maintaining the OpenSSL bindings for Ruby, and I'm considering
> exposing SHA3 and BLAKE digests.
>
> In addition, for the first time, I wrote some tests to test ALL
> algorithms we expose, and found that "DSS", "DSS1" and "SHA" no longer
>
> On Oct 31, 2019, at 7:59 AM, Samuel Williams
> wrote:
>
> I am maintaining the OpenSSL bindings for Ruby, and I'm considering exposing
> SHA3 and BLAKE digests.
>
> In addition, for the first time, I wrote some tests to test ALL algorithms we
> expose, and found that "DSS", "DSS1" and
I am maintaining the OpenSSL bindings for Ruby, and I'm considering
exposing SHA3 and BLAKE digests.
In addition, for the first time, I wrote some tests to test ALL algorithms
we expose, and found that "DSS", "DSS1" and "SHA" no longer exist.
I'm going to assume this algorithm is removed because
