On Wednesday 16 June 2004 12:20 pm, you wrote: > In message <[EMAIL PROTECTED]> on Mon, 14 Jun 2004 > 19:35:08 -0400, Geoff Thorpe <[EMAIL PROTECTED]> said: > > geoff> On June 14, 2004 12:00 pm, Kevin Stefanik wrote: > geoff> > I just realized that we may not have been discussing the same > geoff> > issue. When I was referring to dynamically or statically > geoff> > linked engines, I was referring to how the engines were > geoff> > linked to libcrypto. In all cases, we're discussing a > geoff> > dynamic engine contained in a shared library, so I think we > geoff> > agree on the problem. > geoff> > geoff> Ah, phew. Zoltan sent some stuff to me, but I'll need to wait a > geoff> couple of days until I have time to sift through this. However > geoff> I'm pretty confident the 0.9.7 use of ERR_get_implementation() > geoff> is bogus. > > After reading this thread, I took a look, and yes, that was the wrong > thing to do. My bad. I tried to do what ENGINE_get_static_state() > does, but without implementing that specific function... I understand > now why that wasn't the best idea...
Well, if the gurus didn't make a mistake now and then, there wouldn't be much to an inspire an amateur like myself to stay involved! > > geoff> What results have you had (if any) against cvs snapshots? As > geoff> you've observed, there is a better mechanism in place there and > geoff> depending on what I find when I get a chance to dig into > geoff> Zoltan's mail, I may elect to just merge that aspect of the > geoff> engine code back to 0.9.7 to address the problem. ï suivre ... > > I entirely support merging the ENGINE_get_static_state() code into > 0.9.7. > I think we can make do with a less involved fix, actually, by just backing out the conditional if the engine still _requires_ its own copy of the libcrypto code, or, preferably, just linking to libcrypto dynamically if the earlier requirement no longer holds. I just need an expert's best guess and I'll be out of your hair. Kevin ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
