Please, read INSTALL.W32. Also, please read http://openssl.org/support/faq.html#PROG2 for more information. (This is one of the most frequently asked questions.)
If you can, build OpenSSL yourself. This may not necessarily be practical for you, but if you can it should help a lot. -Kyle H On 6/12/09, patfla <[email protected]> wrote: > > Hi - I'm looking to eventually wrap OpenSSL in Eiffel - the OO language that > we use in house. > > So testing out various things. We're on Windows. I downloaded the Windows > port of OpenSSL from here: > > http://www.slproweb.com/products/Win32OpenSSL.html > > (and sent the author some money via paypal as requested). > > Found some sample and simple C code that uses the OpenSSL api here: > > http://www.rtfm.com/openssl-examples/ > > From here. > > To build, I needed to modify the first lines of the example code's Makefile > as follows: > > OPENSSLDIR=c:/openssl32 > CFLAGS=-g -I$(OPENSSLDIR)/include > LD=-Lc:/openssl32/lib -llibeay32 -lssleay32 > > I sent these Windows mods to the author - no reply. > > With this change to the Makefile the programs appear to compile and link > without error using the cygwin Windows tools. > > I run 'mserver'. There are 3 client variants: pclient, rclient and sclient. > I run pclient (against mserver) on the same machine. Mserver listens on > port 4433. Pclient, looking in the code, seems to proxy somehow. I run it > against mserver and pclient returns saying 'couldn't connect socket'. > > sclient returns with no message. rclient provokes a trace from mclient: > > D:\OpenSSL\examples\one>mserver > 8219 [main] mserver 3044 _cygtls::handle_exceptions: Error while dumping > stat > e (probably corrupted stack) > > but mserver is still running. > > So what do I make of this all? Not sure - I'm totally new to SSL. Have > written tcp/ip socket based programs before but, as I said, don't yet have a > sense of the SSL landscape. > > There isn't a README or instructions with the example code. What little > I've learned so far is from reading the code. Which obviously I'll do more > of. > > It seems that the book to get, even though it's old, (and in particular for > the OpenSSL API) is the following: > > > http://www.amazon.com/Network-Security-with-OpenSSL/dp/B0028N4W3I/ref=sr_1_1?ie=UTF8&s=books&qid=1244829250&sr=8-1 > > Which I'll get shortly but don't have yet. > > > -- > View this message in context: > http://www.nabble.com/OpenSSL-code-on-Windows-crashes.-tp24003641p24003641.html > Sent from the OpenSSL - Dev mailing list archive at Nabble.com. > > ______________________________________________________________________ > OpenSSL Project http://www.openssl.org > Development Mailing List [email protected] > Automated List Manager [email protected] > ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List [email protected] Automated List Manager [email protected]
