Cli: Keys not currently valid for Linux

Created on 14 Jun 2017  路  9Comments  路  Source: heroku/cli

While attempting to verify the heroku-cli package during installation, the following error is being thrown:

W: GPG error: https://cli-assets.heroku.com/branches/stable/apt ./ InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 023F87BAC47B4132
W: The repository 'https://cli-assets.heroku.com/branches/stable/apt ./ InRelease' is not signed.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.

Further investigation of the source took me to the following XML file:

<Error>
<Code>NoSuchKey</Code>
<Message>The specified key does not exist.</Message>
<Key>branches/stable/apt</Key>
...
</Error>

This may not be the right place for this, but there doesn't seem to be any other way to alert the heroku cli team to the issue. If there's something I'm missing, please let me know.

Most helpful comment

I know this is closed, but since it's back and I expect this to happen to others as well: there's no need to run that entire install-ubuntu.sh file again. The only relevant line from that entire script is this:

curl https://cli-assets.heroku.com/apt/release.key | sudo apt-key add -

[EDIT] added sudo as per @cyrillkalita's correction, 3 comments down from this one.

All 9 comments

can you try once more? We just updated our keys

Works like a dream. Thanks!

This is back - @jdxcode can you please update your keys?

benquigley@shamrock:~$ sudo apt update
...
Get:6 https://cli-assets.heroku.com/branches/stable/apt ./ InRelease [2,539 B]                    

Err:6 https://cli-assets.heroku.com/branches/stable/apt ./ InRelease                              
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY C927EBE00F1B0520
...
Reading package lists... Done                                 
W: GPG error: https://cli-assets.heroku.com/branches/stable/apt ./ InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY C927EBE00F1B0520
E: The repository 'https://cli-assets.heroku.com/branches/stable/apt ./ 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.

Thanks!

@BenQuigley looks fine on my end, try using wget -qO- https://cli-assets.heroku.com/install-ubuntu.sh | sh

or even better, just use the snap! sudo snap install heroku

That works. I had followed these instructions on elementaryOS. Anyway, thanks!

I know this is closed, but since it's back and I expect this to happen to others as well: there's no need to run that entire install-ubuntu.sh file again. The only relevant line from that entire script is this:

curl https://cli-assets.heroku.com/apt/release.key | sudo apt-key add -

[EDIT] added sudo as per @cyrillkalita's correction, 3 comments down from this one.

I know this is closed, but since it's back and I expect this to happen to others as well: there's no need to run that entire install-ubuntu.sh file again. The only relevant line from that entire script is this:

curl https://cli-assets.heroku.com/apt/release.key | apt-key add -

good solution. thanks!

curl https://cli-assets.heroku.com/apt/release.key | apt-key add -

Didn't work for me. But re-running the entire script did work.

curl https://cli-assets.heroku.com/apt/release.key | apt-key add -

@dreamcat4 - when you run it, you may have noticed this E: This command can only be used by root

try this:

curl https://cli-assets.heroku.com/apt/release.key | sudo apt-key add -
Was this page helpful?
0 / 5 - 0 ratings