root@localhost:~# curl https://dist.crystal-lang.org/apt/setup.sh | bash
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 200 100 200 0 0 187 0 0:00:01 0:00:01 --:--:-- 187
Executing: /tmp/apt-key-gpghome.zqh9KjVlRg/gpg.1.sh --keyserver keys.gnupg.net --recv-keys 09617FD37CC06B54
gpg: keyserver receive failed: Server indicated a failure
Hit:1 http://ubuntu.c3sl.ufpr.br/ubuntu bionic InRelease
Hit:2 http://ubuntu.c3sl.ufpr.br/ubuntu bionic-updates InRelease
Hit:3 http://ubuntu.c3sl.ufpr.br/ubuntu bionic-backports InRelease
Hit:4 http://ubuntu.c3sl.ufpr.br/ubuntu bionic-security InRelease
Ign:5 http://dl.google.com/linux/chrome/deb stable InRelease
Hit:6 http://dl.google.com/linux/chrome/deb stable Release
Hit:9 https://packages.microsoft.com/repos/vscode stable InRelease
Get:10 https://dist.crystal-lang.org/apt crystal InRelease [2.478 B]
Err:10 https://dist.crystal-lang.org/apt crystal InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 09617FD37CC06B54
Ign:7 http://packages.erlang-solutions.com/debian bionic InRelease
Hit:11 http://packages.erlang-solutions.com/debian bionic Release
Reading package lists... Done
W: GPG error: https://dist.crystal-lang.org/apt crystal InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 09617FD37CC06B54
E: The repository 'https://dist.crystal-lang.org/apt crystal InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
root@localhost:~#
apt-key adv --keyserver keys.gnupg.net --recv-keys 09617FD37CC06B54
Executing: /tmp/apt-key-gpghome.8b8lIFlW2C/gpg.1.sh --keyserver keys.gnupg.net --recv-keys 09617FD37CC06B54
gpg: keyserver receive failed: Server indicated a failure
disregard this problem, it was a networking issue ... the solution is to use hkp protocol using port 80
apt-key adv --keyserver hkp://keys.gnupg.net:80 --recv-keys 09617FD37CC06B54
I think at least one more person had the same problem, so maybe it's worth checking out. Though I was unable to reproduce this.
The problem is with the keys.gnupg.net keyservers. They're incredibly flaky. We should switch away from relying on keyservers at all.
Most helpful comment
disregard this problem, it was a networking issue ... the solution is to use hkp protocol using port 80