Re: ssleay32
This is, unfortunately, not an openssl problem. If you can use 'openssl s_client -connect host:port' to figure out what the connection is doing, it might help you track down what's going on -- but since it's not an openssl problem, we really can't help you. -Kyle H On Wed, Jul 23, 2008 at 12:09 PM, Foreacre, Craig A. CTR <[EMAIL PROTECTED]> wrote: > Hi, > > > > I hope that you can help me with this. > > > > I have an application that uses ssl. I ran some MS updates and now ssl > doesn't work anymore. I have reinstalled IIS, ran windows repair got a later > version of SSLeay32 and libeay32, but to no avail. I used httpwatch and I > get this error > > > > ERROR_INTERNET_SECURITY_CHANNEL_ERROR > > > > I have other servers running IIS with SSL and they work fine. This server > got hosed somehow. > > > > If I try to reregister the dlls the entry point cannot be found. > > > > I have googled this to death and cant come up with anything. > > > > Please HELP! > > > > Thanks in advance, > > > > Craig Foreacre > > Application Developer/Knowledge Content System Manager > > 2090 Child St > > Naval Hospital Jacksonville > > Jacksonville, FL 32214 > > 904.542.9100 > > > > This electronic mail and any attachments may contain information that is > subject to the Privacy Act of 1974 and the Health Insurance Portability and > Accountability Act (HIPAA) of 1996. Use and disclosure of protected health > information is for OFFICIAL USE ONLY, and must be in compliance with these > statutes. If you have inadvertently received this e-mail, please notify the > sender and delete the data without forwarding it or making any copies > > __ OpenSSL Project http://www.openssl.org User Support Mailing Listopenssl-users@openssl.org Automated List Manager [EMAIL PROTECTED]
Re: SSLEAY32
Title: Message Hmm.. Looking at my libeay32, I have a d2i_X509, but no d2i_x509. Perhaps your code just has a typo, and you meant to use the upper case X? Greg Stark[EMAIL PROTECTED] - Original Message - From: Andrew Finnell To: '[EMAIL PROTECTED]' Sent: Tuesday, August 28, 2001 5:23 PM Subject: RE: SSLEAY32 Yes but for some reason d2i_x509 is not exported by ssleay32 nor libeay32.lib. That is what I'm trying to figure out. I link with both of the libraries and call d2i_x509 in one of my methods and during linking I get a undefined symbol for d2i_x509 - Andrew -Original Message-From: Greg Stark [mailto:[EMAIL PROTECTED]] Sent: Tuesday, August 28, 2001 4:09 PMTo: [EMAIL PROTECTED]Subject: Re: SSLEAY32 The library names are different for the win32 build. They are libeay32.lib and ssleay32.lib. Greg Stark[EMAIL PROTECTED] - Original Message - From: Andrew Finnell To: Openssl ([EMAIL PROTECTED]) Sent: Tuesday, August 28, 2001 3:40 PM Subject: SSLEAY32 I have come across a problem I'm not quite sure how to fix. I use d2i_x509 in one of my applications. When I compile on NT I can't find any libssl.lib or libcrypto.lib files all I find is ssleay32.lib so I link against that. It comes up with an undefined symbol _d2i_x509. But if I compile on solaris and link against libssl.so and libcrytp.so it compiles. Why is there a different between the two platforms? - Andrew T. Finnell Software Engineer eSecurity Inc (321) 394-2485
RE: SSLEAY32
Title: Message Yes but for some reason d2i_x509 is not exported by ssleay32 nor libeay32.lib. That is what I'm trying to figure out. I link with both of the libraries and call d2i_x509 in one of my methods and during linking I get a undefined symbol for d2i_x509 - Andrew -Original Message-From: Greg Stark [mailto:[EMAIL PROTECTED]] Sent: Tuesday, August 28, 2001 4:09 PMTo: [EMAIL PROTECTED]Subject: Re: SSLEAY32 The library names are different for the win32 build. They are libeay32.lib and ssleay32.lib. Greg Stark[EMAIL PROTECTED] - Original Message - From: Andrew Finnell To: Openssl ([EMAIL PROTECTED]) Sent: Tuesday, August 28, 2001 3:40 PM Subject: SSLEAY32 I have come across a problem I'm not quite sure how to fix. I use d2i_x509 in one of my applications. When I compile on NT I can't find any libssl.lib or libcrypto.lib files all I find is ssleay32.lib so I link against that. It comes up with an undefined symbol _d2i_x509. But if I compile on solaris and link against libssl.so and libcrytp.so it compiles. Why is there a different between the two platforms? - Andrew T. Finnell Software Engineer eSecurity Inc (321) 394-2485
Re: SSLEAY32
Title: SSLEAY32 The library names are different for the win32 build. They are libeay32.lib and ssleay32.lib. Greg Stark[EMAIL PROTECTED] - Original Message - From: Andrew Finnell To: Openssl ([EMAIL PROTECTED]) Sent: Tuesday, August 28, 2001 3:40 PM Subject: SSLEAY32 I have come across a problem I'm not quite sure how to fix. I use d2i_x509 in one of my applications. When I compile on NT I can't find any libssl.lib or libcrypto.lib files all I find is ssleay32.lib so I link against that. It comes up with an undefined symbol _d2i_x509. But if I compile on solaris and link against libssl.so and libcrytp.so it compiles. Why is there a different between the two platforms? - Andrew T. Finnell Software Engineer eSecurity Inc (321) 394-2485
