OPENSSL_CONF confuses dig, host, nslookup

[Dirk]

HI,

during the development of my project testssl.sh users encountered a bug which was tracked down to the awkward situation that if the environment variable OPENSSL_CONF is defined in a certain way DNS resultion fails

Steps tp reproduce under 14.04 LTS:
--snip
prompt% export OPENSSL_CONF=gost.conf
prompt% cat OPENSSL_CONF
# testssl config file for openssl

openssl_conf = openssl_def

[ openssl_def ]
engines = engine_section

[ engine_section ]
gost = gost_section

[ gost_section ]
engine_id = gost
default_algorithms = ALL
CRYPT_PARAMS = id-Gost28147-89-CryptoPro-A-ParamSet

prompt% host -t a testssl.sh
GOST engine already loaded
11-Sep-2015 18:30:58.591 ENGINE_by_id failed (crypto failure)
11-Sep-2015 18:30:58.591 error:2606A074:engine routines:ENGINE_by_id:no such engine:eng_list.c:417:id=gost
prompt%
--snap

similar with nslookup or dig. See also https://github.com/drwetter/testssl.sh/issues/134 .

Cheers, Dirk

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1494869/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[Dirk (diru)]

(it also affects bind9-host). My humble guess though is a library is the culprit.

[Robie Basak (racb)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. I appreciate the quality of this bug report and I'm sure it'll be helpful to others experiencing the same issue.

This sounds like an upstream bug to me. Please can you verify this by building directly from the appropriate latest upstream sources? If this can be confirmed as an upstream bug, the best route to getting it fixed in Ubuntu in this case would be to file an upstream bug if you're able to do that. Otherwise, I'm not sure what we can do directly in Ubuntu to fix the problem.

If you do end up filing an upstream bug, please link to it from here. Thanks!

[Robie Basak (racb)]

Importance -> Low since I presume that "the environment variable OPENSSL_CONF is defined in a certain way" applies to only a minority of users.

[Dirk (diru)]

Thx for ACK'ing!

It's not happening in 15.10 as reported in https://github.com/drwetter/testssl.sh/issues/134.

I filed this bug with Debian too (not visible yet). Due to limited time however I won't be able to check whether it's in the vanilla sources or someplace else, sorry!