From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: gost.dll required but missing after latest Cygwin update
Date: Wed, 20 Mar 2019 18:43:00 -0000 [thread overview]
Message-ID: <4d111f18-7f78-ab22-481d-700f256136fc@SystematicSw.ab.ca> (raw)
In-Reply-To: <3a4d01d4df41$1a8ca440$4fa5ecc0$@bytehouse.co.uk>
On 2019-03-20 11:19, Alan wrote:
> This seems related to openssl 1.1.1b1 but it affects multiple other
> programs.
>
> For example dig no longer works:
>
> AlanG@Bytehouse-PC-01 ~
> $ dig bytehouse.co.uk any
> 20-Mar-2019 16:52:02.636 ENGINE_by_id failed (crypto failure)
> 20-Mar-2019 16:52:02.637 error:25066067:DSO support
> routines:dlfcn_load:could not load the shared
> library:crypto/dso/dso_dlfcn.c:119:filename(/usr/lib/engines-1.1/gost.dll):
> No such file or directory
> 20-Mar-2019 16:52:02.637 error:25070067:DSO support routines:DSO_load:could
> not load the shared library:crypto/dso/dso_lib.c:162:
> 20-Mar-2019 16:52:02.637 error:260B6084:engine routines:dynamic_load:dso not
> found:crypto/engine/eng_dyn.c:414:
> 20-Mar-2019 16:52:02.637 error:2606A074:engine routines:ENGINE_by_id:no such
> engine:crypto/engine/eng_list.c:334:id=gost
> dig: dst_lib_init: crypto failure
>
> I have been unable so far to find a workaround or fix. There's a libgost.so
> in /usr/lib/engines-1.0 but no gost.dll anywhere:
>
> $ ls -al /usr/lib/engine*
> /usr/lib/engines-1.0:
> total 328
> drwxr-xr-x+ 1 AlanG Domain Users 0 Mar 20 16:50 .
> drwxr-xr-x+ 1 AlanG Domain Users 0 Mar 20 16:51 ..
> -rwxr-xr-x 1 AlanG Domain Users 18963 Mar 11 17:59 lib4758cca.so
> -rwxr-xr-x 1 AlanG Domain Users 18451 Mar 11 17:59 libaep.so
> -rwxr-xr-x 1 AlanG Domain Users 17427 Mar 11 17:59 libatalla.so
> -rwxr-xr-x 1 AlanG Domain Users 8211 Mar 11 17:59 libcapi.so
> -rwxr-xr-x 1 AlanG Domain Users 23059 Mar 11 17:59 libchil.so
> -rwxr-xr-x 1 AlanG Domain Users 22035 Mar 11 17:59 libcswift.so
> -rwxr-xr-x 1 AlanG Domain Users 8211 Mar 11 17:59 libgmp.so
> -rwxr-xr-x 1 AlanG Domain Users 94227 Mar 11 17:59 libgost.so
> -rwxr-xr-x 1 AlanG Domain Users 13843 Mar 11 17:59 libnuron.so
> -rwxr-xr-x 1 AlanG Domain Users 8211 Mar 11 17:59 libpadlock.so
> -rwxr-xr-x 1 AlanG Domain Users 27667 Mar 11 17:59 libsureware.so
> -rwxr-xr-x 1 AlanG Domain Users 19987 Mar 11 17:59 libubsec.so
>
> /usr/lib/engines-1.1:
> total 48
> drwxr-xr-x+ 1 AlanG Domain Users 0 Mar 20 16:51 .
> drwxr-xr-x+ 1 AlanG Domain Users 0 Mar 20 16:51 ..
> -rwxr-xr-x 1 AlanG Domain Users 8211 Mar 11 05:52 capi.dll
> -rwxr-xr-x 1 AlanG Domain Users 12307 Mar 11 05:52 padlock.dll
>
> I've attached a redacted cygcheck file.
+1 for bind-utils - looks related to recent openssl update.
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2019-03-20 18:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-20 17:19 Alan
2019-03-20 18:43 ` Brian Inglis [this message]
2019-03-21 11:58 Alan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4d111f18-7f78-ab22-481d-700f256136fc@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).