When installing MSVS2: "Error retrieving 'some@email' via WKD: General error" repeatedly

[Grant Birchmeier]

I'm trying to remotely guide someone through installing Ruby (he used rubyinstaller-devkit-3.2.2-1-x64.exe), and when he gets to the MSYS2 install phase we are seeing this kinda thing repeatedly:

gpg: error retrieving 'a---.p---@gmail..com' via WKD: General error

gpg: error reading key: General error

gpg: refreshing 1 key from hkps://keyserver.ubuntu.com

gpg: keyserver refresh failed: General error

==> ERROR: Could not update key: F40D263ECA25678A

(Actual email is intentionally altered.)  This occurs 12 times with different email addresses.

Is there a not-too-elaborate way to work around this?  Is this a bug in the installer?  (It sure feels like something that should never happen!)

This guy is a customer of ours, so I don't have much access to his machine.  I just need him to be able to use a ruby script that I wrote, and it's crazy if he can't install ruby because of some key nonsense.

-Grant

[Grant Birchmeier]

Oof-- we now believe this to be caused by a corporate security setting on the guy's computer.  He's working with his IT to investigate it.

[Raphik Bhai]

 I do not understand anything, what has happened, I do not understand anything 

--
You received this message because you are subscribed to the Google Groups "RubyInstaller" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyinstalle...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyinstaller/63d491a9-8495-44cb-bbd1-6135d89d00f5n%40googlegroups.com.

[Grant Birchmeier]

The client has finally gotten back to me.  His IT was not able to solve it.

I apologize for the giant copy/paste, but his install output is below.  Does anyone know what the deal is?

==========================

_____       _           _____           _        _ _         ___

|  __ \     | |         |_   _|         | |      | | |       |__ \

| |__) |   _| |__  _   _  | |  _ __  ___| |_ __ _| | | ___ _ __ ) |

|  _  / | | | '_ \| | | | | | | '_ \/ __| __/ _` | | |/ _ \ '__/ /

| | \ \ |_| | |_) | |_| |_| |_| | | \__ \ || (_| | | |  __/ | / /_

|_|  \_\__,_|_.__/ \__, |_____|_| |_|___/\__\__,_|_|_|\___|_||____|

                    __/ |           _

                   |___/          _|_ _  __   | | o __  _| _     _

                                   | (_) |    |^| | | |(_|(_)\^/_>

 

   1 - MSYS2 base installation

   2 - MSYS2 system update (optional)

   3 - MSYS2 and MINGW development toolchain

 

Which components shall be installed? If unsure press ENTER [1,3]

 

> sh -lc true

'C:\WINDOWS\system32\drivers\etc\hosts' -> '/etc/hosts'

'C:\WINDOWS\system32\drivers\etc\protocol' -> '/etc/protocols'

'C:\WINDOWS\system32\drivers\etc\services' -> '/etc/services'

'C:\WINDOWS\system32\drivers\etc\networks' -> '/etc/networks'

gpg: /etc/pacman.d/gnupg/trustdb.gpg: trustdb created

gpg: no ultimately trusted keys found

gpg: starting migration from earlier GnuPG versions

gpg: porting secret keys from '/etc/pacman.d/gnupg/secring.gpg' to gpg-agent

gpg: migration succeeded

==> Generating pacman master key. This may take some time.

gpg: Generating pacman keyring master key...

gpg: directory '/etc/pacman.d/gnupg/openpgp-revocs.d' created

gpg: revocation certificate stored as '/etc/pacman.d/gnupg/openpgp-revocs.d/B6F8D2FF5B49DD668E5579C156B71AD13A7DCADD.rev'

gpg: Done

==> Updating trust database...

gpg: marginals needed: 3  completes needed: 1  trust model: pgp

gpg: depth: 0  valid:   1  signed:   0  trust: 0-, 0q, 0n, 0m, 0f, 1u

==> Appending keys from msys2.gpg...

==> Locally signing trusted keys in keyring...

  -> Locally signed 5 keys.

==> Importing owner trust values...

gpg: setting ownertrust to 4

gpg: setting ownertrust to 4

gpg: setting ownertrust to 4

gpg: setting ownertrust to 4

gpg: setting ownertrust to 4

==> Disabling revoked keys in keyring...

  -> Disabled 4 keys.

==> Updating trust database...

gpg: marginals needed: 3  completes needed: 1  trust model: pgp

gpg: depth: 0  valid:   1  signed:   5  trust: 0-, 0q, 0n, 0m, 0f, 1u

gpg: depth: 1  valid:   5  signed:   7  trust: 0-, 0q, 0n, 5m, 0f, 0u

gpg: depth: 2  valid:   4  signed:   2  trust: 4-, 0q, 0n, 0m, 0f, 0u

gpg: next trustdb check due at 2023-09-12

gpg: error retrieving 'alexey...@gmail.com' via WKD: General error

gpg: error reading key: General error

gpg: refreshing 1 key from hkps://keyserver.ubuntu.com

gpg: keyserver refresh failed: General error

==> ERROR: Could not update key: F40D263ECA25678A

gpg: error retrieving 'david....@gmail.com' via WKD: General error

gpg: error reading key: General error

gpg: refreshing 1 key from hkps://keyserver.ubuntu.com

gpg: keyserver refresh failed: General error

==> ERROR: Could not update key: 790AE56A1D3CFDDC

gpg: error retrieving 'martel...@gmail.com' via WKD: General error

gpg: error reading key: General error

gpg: refreshing 1 key from hkps://keyserver.ubuntu.com

gpg: keyserver refresh failed: General error

==> ERROR: Could not update key: DA7EF2ABAEEA755C

gpg: error retrieving 'reiter.c...@gmail.com' via WKD: General error

gpg: error reading key: General error

gpg: refreshing 1 key from hkps://keyserver.ubuntu.com

gpg: keyserver refresh failed: General error

==> ERROR: Could not update key: 755B8182ACD22879

gpg: error retrieving 'icqui...@gmail.com' via WKD: General error

gpg: error reading key: General error

gpg: refreshing 1 key from hkps://keyserver.ubuntu.com

gpg: keyserver refresh failed: General error

==> ERROR: Could not update key: 9F418C233E652008

gpg: error retrieving 'mingw....@gmail.com' via WKD: General error

gpg: error reading key: General error

gpg: refreshing 1 key from hkps://keyserver.ubuntu.com

gpg: keyserver refresh failed: General error

==> ERROR: Could not update key: BBE514E53E0D0813

gpg: error retrieving 'ale...@gmail.com' via WKD: General error

gpg: error reading key: General error

gpg: refreshing 1 key from hkps://keyserver.ubuntu.com

gpg: keyserver refresh failed: General error

==> ERROR: Could not update key: 5F92EFC1A47D45A1

gpg: error retrieving 'david....@gmail.com' via WKD: General error

gpg: error reading key: General error

gpg: refreshing 1 key from hkps://keyserver.ubuntu.com

gpg: keyserver refresh failed: General error

==> ERROR: Could not update key: 974C8BE49078F532

gpg: error retrieving 'reiter.c...@gmail.com' via WKD: General error

gpg: error reading key: General error

gpg: refreshing 1 key from hkps://keyserver.ubuntu.com

gpg: keyserver refresh failed: General error

==> ERROR: Could not update key: FA11531AA0AA7F57

gpg: error retrieving 'm...@martellmalone.com' via WKD: No name

gpg: error reading key: No name

gpg: refreshing 1 key from hkps://keyserver.ubuntu.com

gpg: keyserver refresh failed: General error

==> ERROR: Could not update key: 794DCF97F93FC717

gpg: error retrieving 'martel...@gmail.com' via WKD: General error

gpg: error reading key: General error

gpg: refreshing 1 key from hkps://keyserver.ubuntu.com

gpg: keyserver refresh failed: General error

==> ERROR: Could not update key: D595C9AB2C51581E

gpg: error retrieving 'mingw....@gmail.com' via WKD: General error

gpg: error reading key: General error

gpg: refreshing 1 key from hkps://keyserver.ubuntu.com

gpg: keyserver refresh failed: General error

==> ERROR: Could not update key: 4DF3B7664CA56930

MSYS2 seems to be properly installed

Install MSYS2 and MINGW development toolchain ...

> pacman -S --needed --noconfirm autoconf autogen automake-wrapper diffutils file gawk grep libtool m4 make patch sed texinfo texinfo-tex wget mingw-w64-ucrt-x86_64-binutils mingw-w64-ucrt-x86_64-crt-git mingw-w64-ucrt-x86_64-gcc mingw-w64-ucrt-x86_64-gcc-libs mingw-w64-ucrt-x86_64-headers-git mingw-w64-ucrt-x86_64-libmangle-git mingw-w64-ucrt-x86_64-libwinpthread-git mingw-w64-ucrt-x86_64-make mingw-w64-ucrt-x86_64-tools-git mingw-w64-ucrt-x86_64-winpthreads-git pkgconf mingw-w64-ucrt-x86_64-pkgconf

warning: autoconf-wrapper-20221207-1 is up to date -- skipping

warning: autogen-5.18.16-4 is up to date -- skipping

warning: automake-wrapper-20221207-1 is up to date -- skipping

warning: diffutils-3.9-1 is up to date -- skipping

warning: file-5.44-5 is up to date -- skipping

warning: gawk-5.2.1-2 is up to date -- skipping

warning: grep-1~3.0-6 is up to date -- skipping

warning: libtool-2.4.7-3 is up to date -- skipping

warning: m4-1.4.19-2 is up to date -- skipping

warning: make-4.4.1-1 is up to date -- skipping

warning: patch-2.7.6-2 is up to date -- skipping

warning: sed-4.9-1 is up to date -- skipping

warning: texinfo-7.0.3-1 is up to date -- skipping

warning: texinfo-tex-7.0.3-1 is up to date -- skipping

warning: wget-1.21.3-2 is up to date -- skipping

warning: mingw-w64-ucrt-x86_64-binutils-2.40-2 is up to date -- skipping

warning: mingw-w64-ucrt-x86_64-crt-git-10.0.0.r248.g5f566373f-1 is up to date -- skipping

warning: mingw-w64-ucrt-x86_64-gcc-12.2.0-10 is up to date -- skipping

warning: mingw-w64-ucrt-x86_64-gcc-libs-12.2.0-10 is up to date -- skipping

warning: mingw-w64-ucrt-x86_64-headers-git-10.0.0.r248.g5f566373f-1 is up to date -- skipping

warning: mingw-w64-ucrt-x86_64-libmangle-git-10.0.0.r248.g5f566373f-1 is up to date -- skipping

warning: mingw-w64-ucrt-x86_64-libwinpthread-git-10.0.0.r248.g5f566373f-1 is up to date -- skipping

warning: mingw-w64-ucrt-x86_64-make-4.4-2 is up to date -- skipping

warning: mingw-w64-ucrt-x86_64-tools-git-10.0.0.r248.g5f566373f-1 is up to date -- skipping

warning: mingw-w64-ucrt-x86_64-winpthreads-git-10.0.0.r248.g5f566373f-1 is up to date -- skipping

warning: pkgconf-1.9.4-1 is up to date -- skipping

warning: mingw-w64-ucrt-x86_64-pkgconf-1~1.8.0-2 is up to date -- skipping

there is nothing to do

Install MSYS2 and MINGW development toolchain succeeded

 

You can use 'ridk enable' to activate the MSYS2 tools on the command prompt.

 

   1 - MSYS2 base installation

   2 - MSYS2 system update (optional)

   3 - MSYS2 and MINGW development toolchain

 

Which components shall be installed? If unsure press ENTER []

On Sat, Aug 5, 2023 at 10:18 AM Mohit Sindhwani <mo_...@onghu.com> wrote:

On 2023-8-5 5:55 am, Grant Birchmeier wrote:
> Oof-- we now believe this to be caused by a corporate security setting
> on the guy's computer.  He's working with his IT to investigate it.
>

Thanks Grant. If you do find out what, could you share that with us? It
may be helpful to document it some place... if nowhere else, I keep a
"Install Ruby on Windows" page[1] that I update annually - I could try
to adding it there if nowhere else.

[1] Link -
https://notepad.onghu.com/2023/ruby3.2-windows-day0-install-hello_world/

Best wishes,
Mohit.

[Grant Birchmeier]

Oops, sent too hastily.  Meant to add:

1 - After this install, regular Ruby appears to work from DOS.  He was able to execute "ruby --version" without error.  It's the Mingw env that is not installed.

2 - This is the real roadblock-- he can't install a crucial gem.  Trying to install a gem results in this:

C:\Ruby32-x64\ridk_use>gem install nokogiri

ERROR:  SSL verification error at depth 3: self-signed certificate in certificate chain (19)

ERROR:  Root certificate is not trusted (/CN=Avista-Corp-RootCA)

ERROR:  SSL verification error at depth 3: self-signed certificate in certificate chain (19)

ERROR:  Root certificate is not trusted (/CN=Avista-Corp-RootCA)

ERROR:  SSL verification error at depth 3: self-signed certificate in certificate chain (19)

ERROR:  Root certificate is not trusted (/CN=Avista-Corp-RootCA)

ERROR:  Could not find a valid gem 'nokogiri' (>= 0), here is why:

          Unable to download data from https://rubygems.org/ - SSL_connect returned=1 errno=0 peeraddr=151.101.193.227:443 state=error: certificate verify failed (self-signed certificate in certificate chain) (https://rubygems.org/specs.4.8.gz)

ERROR:  SSL verification error at depth 3: self-signed certificate in certificate chain (19)

ERROR:  Root certificate is not trusted (/CN=Avista-Corp-RootCA)

ERROR:  SSL verification error at depth 3: self-signed certificate in certificate chain (19)

ERROR:  Root certificate is not trusted (/CN=Avista-Corp-RootCA)

ERROR:  SSL verification error at depth 3: self-signed certificate in certificate chain (19)

ERROR:  Root certificate is not trusted (/CN=Avista-Corp-RootCA)

[Thierry]

Hi Grant,

I had this kind of situation in the past, and the issue is definitely on the side of the IT of your customer.

In my case, it took them several months to figure it out, and get it right.

In the meantime, if ruby is working, maybe you can transfer the .gem to you customer so that s/he installs it from the file?

Cheers

-- Thierry

[Grant Birchmeier]

I tried having him download the gem directly and install it... but the problem is that the gem has dependencies, and the same SSL problem recurs when rubygems tries to install those.

This is a ridiculous problem, and doesn't make Ruby (which I love) look great in the eyes of my Windows-centric client.

Thierry, if you happen to remember any details of how your IT resolved it, please post them.  

On Wed, Aug 30, 2023 at 3:55 AM Thierry <thyr...@gmail.com> wrote:

Hi Grant,

I had this kind of situation in the past, and the issue is definitely on the side of the IT of your customer.

In my case, it took them several months to figure it out, and get it right.

In the meantime, if ruby is working, maybe you can transfer the .gem to you customer so that s/he installs it from the file?

Cheers

-- Thierry

--
You received this message because you are subscribed to the Google Groups "RubyInstaller" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyinstalle...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/rubyinstaller/aff0cbc5-25ce-4235-9cf5-52df5da6a810n%40googlegroups.com.

[Keith van Jaarsveldt]

Change the key server maybe?

To view this discussion on the web visit https://groups.google.com/d/msgid/rubyinstaller/CAG0qRwNGdJDbJeu_etAZYWL02MADqM1eqt9%3D4AoDrjjeEFGPaw%40mail.gmail.com.

[Grant Birchmeier]

"Change the key server maybe?"

Those words are only slightly meaningful to me.  Can you elaborate?

[Keith van Jaarsveldt]

I may be way off base here, it seems that the keys are not being refreshed, might be something wrong with the key server 

I am not an expert with Ruby so not sure if it has a gpg.conf file, if there isn't one, create one

2. Edit it if it is there.

3. Modify the keyserver line and try a new key server maybe something like hkps://keys.openpgp.org or look for another key server

4. You probably going to need to refresh the keys

Check the the current keyserver syntax is correct before you try this.

I am not saying this will work or is the problem 

On Wed, Aug 30, 2023 at 4:30 PM Grant Birchmeier <gr...@grantb.net> wrote:

"Change the key server maybe?"

Those words are only slightly meaningful to me.  Can you elaborate?

--

You received this message because you are subscribed to the Google Groups "RubyInstaller" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyinstalle...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/rubyinstaller/CAG0qRwO6A8_PLQjeWSt%2BJGniOfjnOrb4qf0rTW9VwAmQdUqAww%40mail.gmail.com.

[Thierry]

Hi Grant,

Unfortunately, it was not my IT (= myself ^_^), but the customer's IT.

I don't know what the problem was, nor how they solved it, sorry.

Good luck.

-- Thierry