Bryan Blackburn blb at
Wed Jul 8 20:50:56 PDT 2009

On Wed, Jul 08, 2009 at 07:30:09PM -0700, Scott Haneda said:
> If I have for example, IO::Socket::SSL, which I am guessing uses
> openssl, what openssl will it use, and how can I find out?

In general, you want to make sure things link to the dependencies installed
with MacPorts.  See


and the entry following that.

> I am having a good deal of trouble getting ASSP to talk over SSL.  It
> has been suspected that it is related to incorrect versions of
> openssl.

Note that in IO::Socket::SSL's specific instance, it doesn't actually use
OpenSSL but the Net::SSLeay module (p5-net-ssleay).  p5-net-ssleay, on my
system, does link to MacPorts' OpenSSL:

$ otool -L /opt/local/lib/perl5/vendor_perl/5.8.9/darwin-*/auto/Net/SSLeay/SSLeay.bundle 
	/opt/local/lib/libssl.0.9.8.dylib (compatibility version 0.9.8, current version 0.9.8)
	/opt/local/lib/libcrypto.0.9.8.dylib (compatibility version 0.9.8, current version 0.9.8)

> It was simple enough to port update openssl and get a newer version.
> And if I type `which openssl` I get the new version in the macports
> area.
> /opt/local/bin/openssl
> However, when it comes to apps that use IO::Socket::SSL, which in
> turn, will call openssl, how can I be sure it is using the correct
> openssl, not the apple one?

Since it goes through Net::SSLeay to make OpenSSL calls, the best method is
the one I list above using otool, to see where the binding to OpenSSL is in
fact linked.

> There are no patche for IO::Socket::SSL, so it is just being
> installed, nothing changed in it to point to a specific openssl.
> Further, p5-event none of the example in IO::Socket::SSL work for me.

I'm not sure what you mean here.


> -- 
> Scott * If you contact me off list replace talklists@ with scott@ *

More information about the macports-dev mailing list