On Fri, Apr 23, 2010 at 21:35, James Mansion <ja...@mansionfamily.plus.com>wrote:
> Amit Ben Shahar wrote: > >> One of the crucial ingredients is ssl using OpenSsl. but we are >> encountering a problem with the 'no OPENSSL_Applink' error. >> as this is a .Net project, there is no way (i can think of) to compile >> with the applink.c file. >> > 1) Why is that crucial? Microsoft provide crypto support on Windows, > albeit with a different interface. What's wrong with > System.Net.Security.SslStream? > > The .Net.Security.SslStream is not working in asynchronous calls, meaning we'd have to implement it in a thread-per-connection paradigm, which is obviously not an option. > 2) Why can't you 'compile with the applink.c file'? You need a talk to it > through p/invoke - you may need to write another glue DLL to do this. If > you can locate an OpenSSL implementation that has been wrapped as a > free-threaded COM service, you might find things easier if you don't know > how to write such glue. You could try looking in Mono's runtime, too, which > I suspect delegates to OpenSsl (tho I haven't checked). As far as i understood it, openSsl looks for the applink implementation in the actual application and not in dlls, but i could have misread that, anyhow i'm not sure i would know how to do that, can you maybe directly to such an implmentation (free-threaded COM) ? - in the meantime i'll try checking in Mono, though i've never ever looked at it yet. maybe i'll get lucky ;) thanks
