# Ubuntu installation doc needs to be updated for use with new GPG keys?

**URL:** <https://discourse.openrobotics.org/t/ubuntu-installation-doc-needs-to-be-updated-for-use-with-new-gpg-keys/20923>\
**Category:** ROS General\
**Created:** [June 14, 2021, 6:29pm UTC](https://discourse.openrobotics.org/t/ubuntu-installation-doc-needs-to-be-updated-for-use-with-new-gpg-keys/20923 "2021-06-14T18:29:03Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![tfoote](https://sea2.discourse-cdn.com/flex022/user_avatar/discourse.openrobotics.org/tfoote/32/3813_2.png) [@tfoote](https://discourse.openrobotics.org/u/tfoote)\
**Post date:** [June 14, 2021, 7:28pm UTC](https://discourse.openrobotics.org/t/ubuntu-installation-doc-needs-to-be-updated-for-use-with-new-gpg-keys/20923/2 "2021-06-14T19:28:17Z")

</div>

As @cottsay mentioned the current instructions should be valid.

> **[New GPG keys deployed for packages.ros.org](https://discourse.openrobotics.org/t/new-gpg-keys-deployed-for-packages-ros-org/9454/10)**
>
> The new public key uses the same private key as before, so that fingerprint is still correct. From a fresh docker pull, I ran these commands and they worked correctly for Ubuntu Bionic and Focal, targeting Melodic and Noetic respectively: $...

We’ve seen that some gpg implementations don’t import new keys to replace existing keys even if the existing key has expired.

But for simplicity of the deployment for users I’ve also updated the gpg key deployment to use the simpler https syntax from: [ROS GPG Key Expiration Incident - ROS General - Open Robotics Discourse](http://discourse.ros.org/t/ros-gpg-key-expiration-incident/20669?u=tfoote)

---

_[View the full topic](https://discourse.openrobotics.org/t/ubuntu-installation-doc-needs-to-be-updated-for-use-with-new-gpg-keys/20923)._