I was about to update my pod to version 0.7.13.0 but run into issues with the signing keys of RVM.
It says there is no public key, but when I import the public keys from mpapis and pkuczynski and relaunch the RVM update command, it still says keys are missing.
My pod is installed on CentOS7 server.
I am running pgp version 2.0.22 (not the version that seems to be bugged)
gpg (GnuPG) 2.0.22
Copyright © 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Full output after
rvm get latest when logged in with diaspora install account:
[root@ns7 diaspora]# su diaspora
[diaspora@ns7 ~]$ cd diaspora/
[diaspora@ns7 diaspora]$ rvm get latest
gpg: Signature made Tue 23 Jul 2019 11:59:45 PM CEST using RSA key ID 39499BDB
gpg: Can’t check signature: No public key
Warning, RVM 1.26.0 introduces signed releases and automated check of signatures when GPG software found. Assuming you trust Michal Papis import the mpapis public key (downloading the signatures).
GPG signature verification failed for ‘/home/diaspora/.rvm/archives/rvm-installer’ - ‘https://raw.githubusercontent.com/rvm/rvm/master/binscripts/rvm-installer.asc’! Try to install GPG v2 and then fetch the public key:
gpg2 --recv-keys 409B6B1796C275462A1703113804BB82D39DC0E3
or if it fails:
command curl -sSL https://rvm.io/mpapis.asc | gpg2 --import -
the key can be compared with:
NOTE: GPG version 2.1.17 have a bug which cause failures during fetching keys from remote server. Please downgrade or upgrade to newer version (if available) or use the second method described above.
bash: return: _ret: numeric argument required
output after importing public keys:
gpg --keyserver hkp://pgp.mit.edu --recv-keys 409B6B1796C275462A1703113804BB82D39DC0E3 7D2BAF1CF37B13E2069D6956105BD0E739499BDB
gpg: requesting key D39DC0E3 from hkp server pgp.mit.edu
gpg: requesting key 39499BDB from hkp server pgp.mit.edu
gpg: key D39DC0E3: “Michal Papis (RVM signing) firstname.lastname@example.org” not changed
gpg: key 39499BDB: “Piotr Kuczynski email@example.com” 2 new signatures
gpg: no ultimately trusted keys found
gpg: Total number processed: 2
gpg: unchanged: 1
gpg: new signatures: 2
Still getting the pgp error about no valid signitures found.
What and how can I / should I change to come over this message so I can update RVM?