Ah, of course! I was so focused on not accessing that routine and not being able to just link in the "obj" files that the obvious solution of using the library properly escaped me! Thanks.
After a "Visual Studio 2012" build in directory: E:\usr_local\src\openssl-1.0.1f_32 I then was able put that change in and to compile and link very easily: cl -IE:\usr_local\src\openssl-1.0.1f_32\inc32 heartbleed.c /c link heartbleed.obj E:\usr_local\src\openssl-1.0.1f_32\out32dll\libeay32.lib E:\usr_local\src\openssl-1.0.1f_32\out32dll\ssleay32.lib I put those two dll files (ssleay32.dll and libeay32.dll) in my directory with the new "exe" from the build and it worked just fine. Thanks again to Tim Hudson, and of course to Rob Stradling for sharing the utility, Steve... On Fri, Apr 11, 2014 at 10:58 PM, Tim Hudson <t...@cryptsoft.com> wrote: > On 11/04/2014 10:38 PM, Steven Kneizys wrote: > > The same issue when I tried to port over to windows, the ssl3_write_bytes > is not exposed in the library. There doesn't seem to be an easy workaround > that I can see. > > > The work around is trivial if you wanted to do that. > > Change to use the SSL_get_ssl_method function. > > This line: > > if (ssl3_write_bytes(v_ssl, TLS1_RT_HEARTBEAT, buf, > 3 + payload + padding) >= 0) > > Simply becomes: > > if (SSL_get_ssl_method(v_ssl)->ssl_write_bytes(v_ssl, > TLS1_RT_HEARTBEAT, buf, > 3 + payload + padding) >= 0) > > Tim. > > -- Steve Kneizys Senior Business Process Engineer Voice: (610) 256-1396 [For Emergency Service (888)864-3282] Ferrilli Information Group -- Quality Service and Solutions for Higher Education web: http://www.ferrilli.com/ <http://www.figsolutions.com/> Making you a success while exceeding your expectations.
