Signal-desktop: linux install fails with: ¨gpg: no valid OpenPGP data found¨ message

Created on 4 Feb 2018 · 13Comments · Source: signalapp/Signal-Desktop

[x] I have searched open and closed issues for duplicates

Bug description

linux install fails with: ¨gpg: no valid OpenPGP data found¨ message

when using:
curl -s https://updates.signal.org/desktop/apt/keys.asc | sudo apt-key add -

Steps to reproduce

issue the following command:
curl -s https://updates.signal.org/desktop/apt/keys.asc | sudo apt-key add -
getting this error message:
gpg: no valid OpenPGP data found.

Actual result:

Expected result:

Screenshots

Platform info

elementary-os .4 loki

Signal version:

latest

Operating System:

Linked device version:

Link to debug log

Bug

Source

wolfieman

Most helpful comment

curl -s https://updates.signal.org/desktop/apt/keys.asc | sudo apt-key add -

curl -O https://updates.signal.org/desktop/apt/keys.asc # download the keys.asc
cat keys.asc # check the keys.asc if the keys.asc is true then next
sudo apt-key add keys.asc # add the keys.asc

tulid on 24 Feb 2020

👍3 🚀1 🎉1

All 13 comments

Hey there! It looks like you had a small change in our recommended command. The included https:// is really important - otherwise, our server will reject the request. This should work for you:

curl -s https://updates.signal.org/desktop/apt/keys.asc | sudo apt-key add -

scottnonnenberg on 6 Feb 2018

👍5

This does not fix the issue, I am still getting the same error!

wolfieman on 8 Feb 2018

Please re-open.

wolfieman on 8 Feb 2018

Please provide the the results of this command:

curl -vs https://updates.signal.org/desktop/apt/keys.asc

You can either provide that output here, or contact me directly.

scottnonnenberg on 8 Feb 2018

curl -vs https://updates.signal.org/desktop/apt/keys.asc

Trying 13.32.80.19...
Trying 2600:9000:2009:f600:16:675e:2280:93a1...
Immediate connect fail for 2600:9000:2009:f600:16:675e:2280:93a1: Network
is unreachable
Trying 2600:9000:2009:1a00:16:675e:2280:93a1...
Immediate connect fail for 2600:9000:2009:1a00:16:675e:2280:93a1: Network
is unreachable
Trying 2600:9000:2009:5600:16:675e:2280:93a1...
Immediate connect fail for 2600:9000:2009:5600:16:675e:2280:93a1: Network
is unreachable
Trying 2600:9000:2009:f400:16:675e:2280:93a1...
Immediate connect fail for 2600:9000:2009:f400:16:675e:2280:93a1: Network
is unreachable
Trying 2600:9000:2009:4200:16:675e:2280:93a1...
Immediate connect fail for 2600:9000:2009:4200:16:675e:2280:93a1: Network
is unreachable
Trying 2600:9000:2009:a200:16:675e:2280:93a1...
Immediate connect fail for 2600:9000:2009:a200:16:675e:2280:93a1: Network
is unreachable
Trying 2600:9000:2009:9a00:16:675e:2280:93a1...
Immediate connect fail for 2600:9000:2009:9a00:16:675e:2280:93a1: Network
is unreachable
Trying 2600:9000:2009:7e00:16:675e:2280:93a1...
Immediate connect fail for 2600:9000:2009:7e00:16:675e:2280:93a1: Network
is unreachable
Connected to updates.signal.org (13.32.80.19) port 443 (#0)
ALPN, offering http/1.1
Cipher selection:
ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH
error setting certificate verify locations:
CAfile: /etc/pki/tls/certs/ca-bundle.crt
CApath: none
Closing connection 0

Cheers!

Wolfgang Sanyer

Software Consultant

+1-919-200-0088

http://goog_56713073

[image: ] https://www.linkedin.com/in/wolfgangsanyer
https://github.com/wolfieman http://sanyer.org

On Thu, Feb 8, 2018 at 4:18 PM, Scott Nonnenberg notifications@github.com
wrote:

Please provide the the results of this command:

curl -vs https://updates.signal.org/desktop/apt/keys.asc

You can either provide that output here, or contact me directly.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/signalapp/Signal-Desktop/issues/2033#issuecomment-364251523,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AALnaTZQAvZ8UyZzM-L09PHaa4YeAu62ks5tS2S3gaJpZM4R4vcz
.

wolfieman on 9 Feb 2018

Command issued via vpn connection:

curl -vs https://updates.signal.org/desktop/apt/keys.asc

Trying 13.32.80.19...
Trying 2600:9000:2009:f600:16:675e:2280:93a1...
Immediate connect fail for 2600:9000:2009:f600:16:675e:2280:93a1: Network is unreachable
Trying 2600:9000:2009:1a00:16:675e:2280:93a1...
Immediate connect fail for 2600:9000:2009:1a00:16:675e:2280:93a1: Network is unreachable
Trying 2600:9000:2009:5600:16:675e:2280:93a1...
Immediate connect fail for 2600:9000:2009:5600:16:675e:2280:93a1: Network is unreachable
Trying 2600:9000:2009:f400:16:675e:2280:93a1...
Immediate connect fail for 2600:9000:2009:f400:16:675e:2280:93a1: Network is unreachable
Trying 2600:9000:2009:4200:16:675e:2280:93a1...
Immediate connect fail for 2600:9000:2009:4200:16:675e:2280:93a1: Network is unreachable
Trying 2600:9000:2009:a200:16:675e:2280:93a1...
Immediate connect fail for 2600:9000:2009:a200:16:675e:2280:93a1: Network is unreachable
Trying 2600:9000:2009:9a00:16:675e:2280:93a1...
Immediate connect fail for 2600:9000:2009:9a00:16:675e:2280:93a1: Network is unreachable
Trying 2600:9000:2009:7e00:16:675e:2280:93a1...
Immediate connect fail for 2600:9000:2009:7e00:16:675e:2280:93a1: Network is unreachable
Connected to updates.signal.org (13.32.80.19) port 443 (#0)
ALPN, offering http/1.1
Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH
error setting certificate verify locations:
CAfile: /etc/pki/tls/certs/ca-bundle.crt
CApath: none
Closing connection 0

wolfieman on 9 Feb 2018

When the command is issued without a vpn connection:
curl -vs https://updates.signal.org/desktop/apt/keys.asc

Trying 54.192.122.206...
Connected to updates.signal.org (54.192.122.206) port 443 (#0)
ALPN, offering http/1.1
Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH
error setting certificate verify locations:
CAfile: /etc/pki/tls/certs/ca-bundle.crt
CApath: none
Closing connection 0

wolfieman on 9 Feb 2018

Looks like you might have a configuration problem on your machine, where curl is looking for your root certificate authorities in the wrong place. Maybe this stack overflow issue will help? https://stackoverflow.com/questions/3160909/how-do-i-deal-with-certificates-using-curl-while-trying-to-access-an-https-url

scottnonnenberg on 9 Feb 2018

That stackoverflow post helped!

I was able to install afterwards.

One caveat: these lines are actually just one:
echo "deb [arch=amd64] https://updates.signal.org/desktop/apt xenial main" | sudo tee -a /etc/apt/sources.list.d/signal-xenial.list

Thanks!

wolfieman on 15 Feb 2018

curl https://bazel.build/bazel-release.pub... | sudo apt-key add -
verify locations:
CAfile: /etc/pki/tls/certs/ca-bundle.crt
CApath: none
gpg: no valid OpenPGP data found.

can not fix yet

husnejahan on 15 Jul 2018

curl -vs https://updates.signal.org/desktop/apt/keys.asc

Trying 13.33.148.127...

Connected to updates.signal.org (13.33.148.127) port 443 (#0)
ALPN, offering http/1.1
Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH
error setting certificate verify locations:
CAfile: /etc/pki/tls/certs/ca-bundle.crt
CApath: none
Closing connection 0 @scottnonnenberg

husnejahan on 15 Jul 2018

I had the same problem, for me the issue was connected with curl, which wasn't installed properly.
Anyway, this link was my first google search result, maybe my experience will help somebody.