Bart,
On Mon, Apr 23, 2018, at 6:45 AM, Bart Van Assche wrote:
> On 04/23/18 00:34, Keith Mendoza wrote:
> > Even with the -std=c89 flag the issue is still present. I was able to
> > replicate the issue with the following code:
> >
> > === BEGIN C CODE ===
> > #include
> > #define OPENSSL_NO_SH
On 04/23/18 00:34, Keith Mendoza wrote:
Even with the -std=c89 flag the issue is still present. I was able to replicate
the issue with the following code:
=== BEGIN C CODE ===
#include
#define OPENSSL_NO_SHA512
#include
const EVP_MD *getType()
{
const EVP_MD *ret;
ret = (const EVP_
Bart,
On Sun, Apr 22, 2018, at 4:59 PM, Keith Mendoza wrote:
> Bart,
> I was hoping to discuss with you on IRC; but, you're not online.
>
> On Sun, Apr 22, 2018, at 4:10 PM, Bart Van Assche wrote:
> > On 04/22/18 08:35, Keith Mendoza wrote:
> > > Bart,
> > > I was actually working on this yester
Bart,
I was hoping to discuss with you on IRC; but, you're not online.
On Sun, Apr 22, 2018, at 4:10 PM, Bart Van Assche wrote:
> On 04/22/18 08:35, Keith Mendoza wrote:
> > Bart,
> > I was actually working on this yesterday. This is what I know so far after
> > a few hours of digging into this:
On 04/22/18 08:35, Keith Mendoza wrote:
Bart,
I was actually working on this yesterday. This is what I know so far after a
few hours of digging into this: It appears that there's an issue with getting
to the memory address that EVP_sha512() returns when it's called in
sc_get_openssl_hashfn().
Bart,
I was actually working on this yesterday. This is what I know so far after a
few hours of digging into this: It appears that there's an issue with getting
to the memory address that EVP_sha512() returns when it's called in
sc_get_openssl_hashfn(). Why this is so, I don't know. Below are de
