From info at jensteich.de Sat Jan 25 15:39:16 2014 From: info at jensteich.de (Jens Teich) Date: Sat, 25 Jan 2014 16:39:16 +0100 Subject: ssl problem In-Reply-To: References: <52E3B886.3050501@jensteich.de> Message-ID: <52E3DAA4.9010401@jensteich.de> Great, now it works at least on Win (didn't try Mac yet). Many thanks for your help. I had to make a minor modification to drakma like this: file request.lisp line 584 --- (comm:attach-ssl http-stream :ssl-side :client) +++ (comm:attach-ssl http-stream :ssl-side :client :ssl-ctx :v3) Are you interested in a patch which allows to set this? Regards Jens Am 25.01.2014 15:17, schrieb Edi Weitz: > A plug-in is itself a shared library and thus the way the SSL libs are > loaded is certainly different from how they are loaded from a > stand-alone executable you delivered. Without having looked up the > details I'd think that the SSL libs are expected in a place where > FileMaker itself would search for them. Did you put the ones you want > loaded in the same folder as FileMaker? > > On Sat, Jan 25, 2014 at 2:13 PM, Jens Teich wrote: >> I want to use >> >> (require "comm") >> >> (comm:ensure-ssl) >> >> in a FileMaker plugin built with fm-plugin-tools. >> >> In the listener it is no problem and even when using the hello-world >> delivery example from LW these two lines work without setting any openssl >> paths. >> >> I am working both on MacOSX 10.8 and Win7 with LW 6.1. >> >> I posted this already on Lispworks list >> (http://article.gmane.org/gmane.lisp.lispworks.general/12755) and got a >> bunch of hints but was not able yet to make it work in a FM plugin. When I >> try it, I get either an error ('unable to load library') or an outdated >> version of openssl loaded. >> >> So obviously fm-plugin-tools is changing something that makes the ssl >> library unusable. Any hints are welcome which help me out of this. >> >> Thanks >> Jens >> From info at jensteich.de Sat Jan 25 13:13:42 2014 From: info at jensteich.de (Jens Teich) Date: Sat, 25 Jan 2014 14:13:42 +0100 Subject: ssl problem Message-ID: <52E3B886.3050501@jensteich.de> I want to use (require "comm") (comm:ensure-ssl) in a FileMaker plugin built with fm-plugin-tools. In the listener it is no problem and even when using the hello-world delivery example from LW these two lines work without setting any openssl paths. I am working both on MacOSX 10.8 and Win7 with LW 6.1. I posted this already on Lispworks list (http://article.gmane.org/gmane.lisp.lispworks.general/12755) and got a bunch of hints but was not able yet to make it work in a FM plugin. When I try it, I get either an error ('unable to load library') or an outdated version of openssl loaded. So obviously fm-plugin-tools is changing something that makes the ssl library unusable. Any hints are welcome which help me out of this. Thanks Jens From edi at agharta.de Sat Jan 25 14:17:44 2014 From: edi at agharta.de (Edi Weitz) Date: Sat, 25 Jan 2014 15:17:44 +0100 Subject: ssl problem In-Reply-To: <52E3B886.3050501@jensteich.de> References: <52E3B886.3050501@jensteich.de> Message-ID: A plug-in is itself a shared library and thus the way the SSL libs are loaded is certainly different from how they are loaded from a stand-alone executable you delivered. Without having looked up the details I'd think that the SSL libs are expected in a place where FileMaker itself would search for them. Did you put the ones you want loaded in the same folder as FileMaker? On Sat, Jan 25, 2014 at 2:13 PM, Jens Teich wrote: > I want to use > > (require "comm") > > (comm:ensure-ssl) > > in a FileMaker plugin built with fm-plugin-tools. > > In the listener it is no problem and even when using the hello-world > delivery example from LW these two lines work without setting any openssl > paths. > > I am working both on MacOSX 10.8 and Win7 with LW 6.1. > > I posted this already on Lispworks list > (http://article.gmane.org/gmane.lisp.lispworks.general/12755) and got a > bunch of hints but was not able yet to make it work in a FM plugin. When I > try it, I get either an error ('unable to load library') or an outdated > version of openssl loaded. > > So obviously fm-plugin-tools is changing something that makes the ssl > library unusable. Any hints are welcome which help me out of this. > > Thanks > Jens > From edi at agharta.de Sat Jan 25 16:41:22 2014 From: edi at agharta.de (Edi Weitz) Date: Sat, 25 Jan 2014 17:41:22 +0100 Subject: ssl problem In-Reply-To: <52E3DAA4.9010401@jensteich.de> References: <52E3B886.3050501@jensteich.de> <52E3DAA4.9010401@jensteich.de> Message-ID: Drakma is maintained by Hans H?bner now. This is where patches are to be sent: https://github.com/edicl/ On Sat, Jan 25, 2014 at 4:39 PM, Jens Teich wrote: > Great, now it works at least on Win (didn't try Mac yet). > Many thanks for your help. > > I had to make a minor modification to drakma like this: > > file request.lisp line 584 > > --- (comm:attach-ssl http-stream :ssl-side :client) > +++ (comm:attach-ssl http-stream :ssl-side :client :ssl-ctx :v3) > > Are you interested in a patch which allows to set this? > > Regards > Jens > > > Am 25.01.2014 15:17, schrieb Edi Weitz: > >> A plug-in is itself a shared library and thus the way the SSL libs are >> loaded is certainly different from how they are loaded from a >> stand-alone executable you delivered. Without having looked up the >> details I'd think that the SSL libs are expected in a place where >> FileMaker itself would search for them. Did you put the ones you want >> loaded in the same folder as FileMaker? >> >> On Sat, Jan 25, 2014 at 2:13 PM, Jens Teich wrote: >>> >>> I want to use >>> >>> (require "comm") >>> >>> (comm:ensure-ssl) >>> >>> in a FileMaker plugin built with fm-plugin-tools. >>> >>> In the listener it is no problem and even when using the hello-world >>> delivery example from LW these two lines work without setting any openssl >>> paths. >>> >>> I am working both on MacOSX 10.8 and Win7 with LW 6.1. >>> >>> I posted this already on Lispworks list >>> (http://article.gmane.org/gmane.lisp.lispworks.general/12755) and got a >>> bunch of hints but was not able yet to make it work in a FM plugin. When >>> I >>> try it, I get either an error ('unable to load library') or an outdated >>> version of openssl loaded. >>> >>> So obviously fm-plugin-tools is changing something that makes the ssl >>> library unusable. Any hints are welcome which help me out of this. >>> >>> Thanks >>> Jens >>> >