Hi!
I just looked on GitHub and I see the reason you reverted the change is that
TerminateProcess is asynchronous.
That is technically true, but I think it's probably synchronous "enough" for
your purposes, since a call to TerminateProcess suspends execution of all
threads in the target proce
On Wed Jun 15 17:42:58 2016, rsalz wrote:
> OpenSSL_1_0_2-stable 75f9068 RT4526: Call TerminateProcess, not ExitProcess
> master 9c1a9cc RT4526: Call TerminateProcess, not ExitProcess
>
> Author: Rich Salz
> Date: Tue Jun 14 16:19:37 2016 -0400
>
> RT4526: Call TerminateProcess, not ExitProcess
>
OpenSSL_1_0_2-stable 75f9068 RT4526: Call TerminateProcess, not ExitProcess
master 9c1a9cc RT4526: Call TerminateProcess, not ExitProcess
Author: Rich Salz
Date: Tue Jun 14 16:19:37 2016 -0400
RT4526: Call TerminateProcess, not ExitProcess
Reviewed-by: Richard Levitte
--
Ticket here: http://
Hi,
I'm working in the 1.0.2g version of OpenSSL, in a Windows desktop environment,
specifically Win 7, 8.1, and 10 (and their equivalent server and R2 versions).
Problem and Resolution:
The following lines of code make use of the Microsoft API ExitProcess:
Apps\Speed.c line 335: ExitProcess(
