index %= st_num.;
>
> Thanks for your help
>
>
> From: Matt Caswell via RT [mailto:r...@openssl.org]
> Sent: 18 June 2016 00:08
> To: Mick Saxton
> Cc: openssl-dev@openssl.org
> Subject: Re: [openssl-dev] [openssl.org #4545] Crash in crypto/rand/md_rand.c
>
>
>
dex %= st_num.;
Thanks for your help
From: Matt Caswell via RT [mailto:r...@openssl.org]
Sent: 18 June 2016 00:08
To: Mick Saxton
Cc: openssl-dev@openssl.org
Subject: Re: [openssl-dev] [openssl.org #4545] Crash in crypto/rand/md_rand.c
On 17/06/16 20:56, Matt Caswell via RT wrote:
>
>
>
On 17/06/16 20:56, Matt Caswell via RT wrote:
>
>
> On 17/06/16 19:43, Mick Saxton via RT wrote:
>> Perhaps we should consider if there are any negative consequences to my
>> solution?
>> It does work.
>>
>> I am trying really hard to get contention but I am only seeing this problem
>> in
>
>
>
>
> From: Salz, Rich via RT [mailto:r...@openssl.org]
> Sent: 17 June 2016 18:39
> To: Mick Saxton
> Cc: openssl-dev@openssl.org
> Subject: RE: [openssl-dev] [openssl.org #4545] Crash in crypto/rand/md_rand.c
>
> Sending mail re-opens the ticket.
>
&
6 18:39
To: Mick Saxton
Cc: openssl-dev@openssl.org
Subject: RE: [openssl-dev] [openssl.org #4545] Crash in crypto/rand/md_rand.c
Sending mail re-opens the ticket.
Rats, wish it was fixed. Going to need something to more easily reproduce it, I
guess.
--
Ticket here:
http://rt.openssl.org
Sending mail re-opens the ticket.
Rats, wish it was fixed. Going to need something to more easily reproduce it,
I guess.
--
Ticket here: http://rt.openssl.org/Ticket/Display.html?id=4545
Please log in as guest with password guest if prompted
--
openssl-dev mailing list
To unsubscribe:
Hi Rich
Many thanks for doing that – unfortunately it is not the whole fix.
I checked out the latest v1.0.2i-dev and built that but I still get the crash.
I know the ticket is now “closed” – do you need me to reopen it?
I am still convinced that I don’t get it with the “master” build – but that
Hi Rich
Sorry for delay in responding – it takes longer to say that an intermittent
problem doesn’t exist than to see it happen once.
I have tested against latest master (15 June) and the v1.1-pre5 – so far both
are looking good.
As a control, I went back and retested with v1.0.2h on the same
On 27/05/16 11:07, Mick Saxton via RT wrote:
> Hi Matt
>
> The test program runs against our major new development so I cannot share it
> as is.
>
> I will try to produce a skeleton version which I could let you have.
>
> - But that will be end if next week as I am away for a few
On 27/05/16 11:07, Mick Saxton via RT wrote:
> Hi Matt
>
> The test program runs against our major new development so I cannot share it
> as is.
>
> I will try to produce a skeleton version which I could let you have.
>
> - But that will be end if next week as I am away for a few
Hi Matt
The test program runs against our major new development so I cannot share it as
is.
I will try to produce a skeleton version which I could let you have.
- But that will be end if next week as I am away for a few days
- That is providing that exhibits the bug.
Mick
Hello,
I can confirm that I have seen a similar behavior in multi-thread
environment. Unfortunately, I do not have a script to reproduce it either.
On Fri, May 20, 2016 at 6:49 PM, Mick Saxton via RT wrote:
> Hi
>
> Before going any further I would like to state that I have
Hello,
I can confirm that I have seen a similar behavior in multi-thread
environment. Unfortunately, I do not have a script to reproduce it either.
On Fri, May 20, 2016 at 6:49 PM, Mick Saxton via RT wrote:
> Hi
>
> Before going any further I would like to state that I have
13 matches
Mail list logo