On Apr 20, 2012, at 5:38 PM, Daniel J. Luke wrote: > On Apr 20, 2012, at 7:25 PM, Bradley Giesbrecht wrote: >> On Apr 20, 2012, at 3:26 PM, Daniel J. Luke wrote: >>> On Apr 20, 2012, at 4:39 PM, Bradley Giesbrecht wrote: >>>> On Apr 20, 2012, at 1:13 PM, John Ruschmeyer wrote: >>>>> Anybody else on Leopard and/or PPC having problems with the upgrade to >>>>> OpenSSL 1.0.1a_0? >>>> >>>> Issues with use: >>>> https://trac.macports.org/ticket/33715 >>> >>> This is about 1.0.1, I believe it is fixed in 1.0.1a (it looks like it >>> according to the changelog - I wasn't affected, so I don't have a test case >>> to verify, though). >> >> In my tests the patch at OpenSSL head does not fix my test cases. If it had >> I would have submitted a port patch. > > It's not clear to me what you're referring to there. > > The patch I referred to fixes the build on 10.5/ppc (actually on all > non-intel builds). I verified that it builds and passes the openssl test > suite with it. > > If you're referring to upstream's 1.0.1a release (or some other patch) not > fixing the tls problem you were seeing with 1.0.1 - I would suggest that you > follow up with upstream.
Yes, I am referring to the unresolved tls problem. Curl can work around the problem but I have found no workaround for openldap for example. It also looks like php soap is broke if you need to make a secure soap call. Regards, Bradley Giesbrecht (pixilla)
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ macports-users mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
