Just like every web browser expands until it can read mail, every modular
authormiod <miod@openbsd.org>
Tue, 15 Apr 2014 20:13:07 +0000 (20:13 +0000)
committermiod <miod@openbsd.org>
Tue, 15 Apr 2014 20:13:07 +0000 (20:13 +0000)
commitaa4ce95a018970caf682a1bbe89179fc85464fd0
tree61a157a011293c509c365171d7a99cb9b83e2033
parent68c0184592b044f3976f88a8512516f3a3780200
Just like every web browser expands until it can read mail, every modular
library expands until it has its own dlfcn wrapper, and libcrypto is no
exception.

Remove the non-dlfcn DSO methods.

This causes public DSO_METHOD_{beos,dl,vms,win32} to disappear (major bump
coming soon). Note that portable software ought to use DSO_METHOD_openssl
instead of picking the backend directly (which makes one wonder why the
backends are exposed, as it is unlikely that more than one can work on
your system).

ok beck@ deraadt@
15 files changed:
lib/libcrypto/crypto/Makefile
lib/libcrypto/dso/dso.h
lib/libcrypto/dso/dso_beos.c [deleted file]
lib/libcrypto/dso/dso_dl.c [deleted file]
lib/libcrypto/dso/dso_dlfcn.c
lib/libcrypto/dso/dso_openssl.c
lib/libcrypto/dso/dso_vms.c [deleted file]
lib/libcrypto/dso/dso_win32.c [deleted file]
lib/libssl/src/crypto/dso/dso.h
lib/libssl/src/crypto/dso/dso_beos.c [deleted file]
lib/libssl/src/crypto/dso/dso_dl.c [deleted file]
lib/libssl/src/crypto/dso/dso_dlfcn.c
lib/libssl/src/crypto/dso/dso_openssl.c
lib/libssl/src/crypto/dso/dso_vms.c [deleted file]
lib/libssl/src/crypto/dso/dso_win32.c [deleted file]