Date: Tue, 5 Apr 2005 20:49:55 +0200 (CEST) From: Ales Krenek <ljocha@ics.muni.cz> To: FreeBSD-gnats-submit@FreeBSD.org Subject: bin/79570: Dynamic OpenSSL engine load disabled Message-ID: <200504051849.j35IntXY021561@balkis.ics.muni.cz> Resent-Message-ID: <200504051900.j35J0HCd043513@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 79570 >Category: bin >Synopsis: Dynamic OpenSSL engine load disabled >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Apr 05 19:00:17 GMT 2005 >Closed-Date: >Last-Modified: >Originator: Ales Krenek >Release: FreeBSD 5.3-RELEASE-p6 i386 >Organization: >Environment: System: FreeBSD balkis.ics.muni.cz 5.3-RELEASE-p6 FreeBSD 5.3-RELEASE-p6 #6: Thu Mar 31 16:10:23 CEST 2005 toor@balkis.ics.muni.cz:/usr/5.3/src/sys/i386/compile/BALKIS i386 >Description: An attempt to load crypto engine dynamically into libcrypto fails. The reason is that none of the available DSO methods is enabled -- when compiling /usr/src/crypto/openssl/crypto/dso/dso_openssl.c DSO_METHOD_openssl() falls back to DSO_METHOD_null(). Having enabled DSO_METHOD_dlfcn (see Fix:) I managed to use the opensc engine to access my hw token, hence I believe there is no serious reason to disable this feature. >How-To-Repeat: >Fix: Make the symbols DSO_DLFCN, HAVE_DLFCN_H defined when compiling in /usr/src/secure/lib/libcrypto >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200504051849.j35IntXY021561>