-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
hi all,
i'm thinking this needs big brain attention on the dev list ...
i've 0.9.8b built from src on OSX 10.4.7.
fwiw, i'm attempting to implement TLS in a Cyrus IMAPd server.
when i test the server's install with:
% openssl
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Richard schrieb:
hi all,
Hello Richard,
i'm thinking this needs big brain attention on the dev list ...
No.
It doesn't
i've 0.9.8b built from src on OSX 10.4.7.
when i test the server's install with:
% openssl s_client -connect
As for libz.so ... think it should be trying to load libz.dylib as that
is the only thing that will exist on the system (since MacOSX
differentiates between DSO's and Dynamic Libraries, but you can
still dlopen() a .dylib, just dlclose() won't actually do anything
as it will remain loaded in your
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
16458:error:25066067:DSO support routines:DLFCN_LOAD:could not load the
shared library:dso_dlfcn.c:162:filename(libz.so): dlopen(libz.so, 2):
^^^
great. why is openssl looking for libz.*so*
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
hi,
per my immediately prior post, rebuilding openssl w/:
./Configure \
...
--- zlib-dynamic \
+++ zlib \
...
these:
% openssl engine 4758cca
16458:error:25066067:DSO support routines:DLFCN_LOAD:could not load the
shared library:dso_dlfcn.c:162:filename(libz.so): dlopen(libz.so, 2):
^^^
great. why is openssl looking for libz.*so* on a _mac_ in the first place?
Because
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
hi brad,
great. why is openssl looking for libz.*so* on a _mac_ in the first
place?
Because DSO_convert_filename(dso, NULL) called from dlfcn_load(),
which calls dlfcn_name_converter() is only expecting to load DSO's.
As explained in my
% openssl engine gmp
10543:error:2506406A:DSO support routines:DLFCN_BIND_FUNC:could
not
bind to the requested symbol name:dso_dlfcn.c:261:symname(bind_engine):
dlsym(0x201070, bind_engine): symbol not found
10543:error:2506C06A:DSO support
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
If you would just compare engines/e_gmp.c to one of the others, you'd
see the problem.
i'm honestly not the one to be poring over openssl's code -- as has been
pointed out to me my this list's members quite awhile ago.
just trying to be
