At 03:30 PM 3/2/2004 -0600, Jason writeth: >Hello everyone. I'm new to the list and happy to be here. I've just >managed to compile OpenSSL on my WinXP box and I created a walkthrough (for >my own reference, but hopefully may help someone) and posted it at >http://www.verysimple.com/support/viewtopic.php?t=89 > >Anyway, I'm getting set to write a PHP (perhaps perl as well) form mail >processor that sends SMIME messages from either nix or win boxes that can be >decrypted in Outlook. I'm sorry to bore you all with my petty project, >however, if anyone has any links or info that would be useful, please feel >free to let me know.
I just looked at the site. Just an FYI, you do need the full Visual C++ compiler suite to compile using nmake...and not everyone has access to or can afford Visual C++. Also, you are supposed to put MASM into the VC++ \bin directory and modifying your path is unnecessary if you run vcvars32.bat. Also, without the MASM compilation, your build would be worthless performance-wise. Now, I have to ask why you went to the trouble of doing all of that when the Win32 OpenSSL Installation Project does that and much more: http://www.slproweb.com/products/Win32OpenSSL.html Those are default binary builds of the latest official OpenSSL source. They come with pre-made libraries to link your applications against for Visual C++ 5/6, Borland C++ Builder 4/5/6, and MinGW. It also comes with pre-compiled Perl modules of Net::SSLeay and Crypto::SSLeay for e-Commerce purposes for both Perl 5.6.x and 5.8.x. Finally, the whole package is wrapped up in a nice wizard-style installer for Windows and does all sorts of auto-configuring to make the experience go smoothly. Your current environment, unless you know OpenSSL's guts inside-out, is probably incorrect as install.w32 doesn't tell you everything that has to be done. It will work for doing most things, but let me recommend that you at least forward users to Win32 OpenSSL who have difficulty following your directions (or have problems with the result). One other reason to use Win32 OpenSSL is for security updates - the Win32 OpenSSL Installation Project is usually updated as soon as possible after a security patch is released. This simplifies distribution of updated binaries to end-users...just point them at the Win32 OpenSSL website to download the latest version and install it. Hope this helps! Thomas J. Hruska -- [EMAIL PROTECTED] Shining Light Productions -- "Meeting the needs of fellow programmers" http://www.slproweb.com/ `'*-~.,_,.~-*'`'*-~.,_,.~-*'`'*-~.,_,.~-*'`'*-~.,_,.~-*'`'*-~.,_,.~-*'`'*-~ Tired of programming languages that are expensive or difficult to use? Try Nuclear Vision today! http://www.slproweb.com/products/nvml.html Announcing Nuclear Vision v2.0, the 100% HTML-style scripting language. Easy to learn, easy to use. ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
