Skip to main content
Unix & Linux

Return to Question

Notice removed Draw attention by Naps62
Bounty Ended with MAQ's answer chosen by Naps62
added 276 characters in body
Source Link
Naps62
Naps62
  • 113
  • 2
  • 9

I'm finding that a few commands (for now dig and nslookup) that fail no matter what with the following output:

19-Jan-2016 15:01:50.219 ENGINE_by_id failed (crypto failure) 19-Jan-2016 15:01:50.219 error:2606A074:engine routines:ENGINE_by_id:no such engine:eng_list.c:389:id=gost dig: dst_lib_init: crypto failure

Even stuff like dig -h results in this, so I'm guessingI guess this happens before the actual command execution starts

I remember these commands used to work, but they're not something I used very often, so I can't exactly pinpoint the origin

I can, however, say that I have messed with ssl options recently. Particularly, I was having problems handling GPG keys, and had to run export OPENSSL_CONF=/etc/ssl/openssl.cnf in order to make it work I also found this issue, which seems to be similar. But that project has nothing to do with what I'm doing, and their solution (unsettingsunsetting OPENSSL_CONF) did not work for me

EDIT: I'm running Arch Linux. The only change I did regarding OpenSSL configurations was running export OPENSSL_CONF=/etc/ssl/openssl.cnf which I needed to use gpg, but I already tried unsetting that

Running unset OPENSSL_CONF; dig -h results in the same output

I'm finding that a few commands (for now dig and nslookup) that fail no matter what with the following output:

19-Jan-2016 15:01:50.219 ENGINE_by_id failed (crypto failure) 19-Jan-2016 15:01:50.219 error:2606A074:engine routines:ENGINE_by_id:no such engine:eng_list.c:389:id=gost dig: dst_lib_init: crypto failure

Even stuff like dig -h results in this, so I'm guessing this happens before the actual command execution starts

I remember these commands used to work, but they're not something I used very often, so I can't exactly pinpoint the origin

I can however say that I have messed with ssl options recently. Particularly, I was having problems handling GPG keys, and had to run export OPENSSL_CONF=/etc/ssl/openssl.cnf in order to make it work I also found this issue, which seems to be similar. But that project has nothing to do with what I'm doing, and their solution (unsettings OPENSSL_CONF) did not work for me

I'm finding that a few commands (for now dig and nslookup) that fail no matter what with the following output:

19-Jan-2016 15:01:50.219 ENGINE_by_id failed (crypto failure) 19-Jan-2016 15:01:50.219 error:2606A074:engine routines:ENGINE_by_id:no such engine:eng_list.c:389:id=gost dig: dst_lib_init: crypto failure

Even stuff like dig -h results in this, so I guess this happens before the actual command execution starts

I remember these commands used to work, but they're not something I used very often, so I can't exactly pinpoint the origin

I can, however, say that I have messed with ssl options recently. Particularly, I was having problems handling GPG keys, and had to run export OPENSSL_CONF=/etc/ssl/openssl.cnf in order to make it work I also found this issue, which seems to be similar. But that project has nothing to do with what I'm doing, and their solution (unsetting OPENSSL_CONF) did not work for me

EDIT: I'm running Arch Linux. The only change I did regarding OpenSSL configurations was running export OPENSSL_CONF=/etc/ssl/openssl.cnf which I needed to use gpg, but I already tried unsetting that

Running unset OPENSSL_CONF; dig -h results in the same output

Notice added Draw attention by Naps62
Bounty Started worth 50 reputation by Naps62
Source Link
Naps62
Naps62
  • 113
  • 2
  • 9

"crypto failure" error when running various commands

I'm finding that a few commands (for now dig and nslookup) that fail no matter what with the following output:

19-Jan-2016 15:01:50.219 ENGINE_by_id failed (crypto failure) 19-Jan-2016 15:01:50.219 error:2606A074:engine routines:ENGINE_by_id:no such engine:eng_list.c:389:id=gost dig: dst_lib_init: crypto failure

Even stuff like dig -h results in this, so I'm guessing this happens before the actual command execution starts

I remember these commands used to work, but they're not something I used very often, so I can't exactly pinpoint the origin

I can however say that I have messed with ssl options recently. Particularly, I was having problems handling GPG keys, and had to run export OPENSSL_CONF=/etc/ssl/openssl.cnf in order to make it work I also found this issue, which seems to be similar. But that project has nothing to do with what I'm doing, and their solution (unsettings OPENSSL_CONF) did not work for me