As far as I know, the SSL functions are not advertised as being
part of any framework on OS X. They are supposed to be accessed
directly from the libssl dylib. Examining my Panther system, I
can't see anything obvious that explains why the bundle calls were
working for you even on Panther.
CFBundle has long permitted very sloppy practices on the part of CFM
code, for compatibility reasons--some early sample code, I believe,
spread mistaken ideas that happened to work on the first versions of
Mac OS X, until the mistake could no longer be corrected.
The intent of CFBundleGetFunctionPointerForName is that the symbol to
be looked up should come from the bundle specified. In the case of
an umbrella framework, this includes symbols from any subframework,
but not from anything else that may happen to be loaded.
However, when it is called from CFM, CFBundle will perform a global
search, as a last resort and purely as a compatibility measure.
Nevertheless, the symbol must be present for the search to succeed,
and from the description of this problem, it sounds as though the
necessary library may not even be loaded in the failing executable.
In that case the solution would be as simple as loading it, using any
of the dyld APIs (for Tiger, the recommended one would be dlopen).
