# We're still using apt-key in 2023?

**URL:** <https://forum.clockworkpi.com/t/were-still-using-apt-key-in-2023/10798>\
**Category:** uConsole\
**Created:** [August 29, 2023, 1:24am UTC](https://forum.clockworkpi.com/t/were-still-using-apt-key-in-2023/10798 "2023-08-29T01:24:37Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![barry99705](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.clockworkpi.com/barry99705/32/6771_2.png) [@barry99705](https://forum.clockworkpi.com/u/barry99705)\
**Post date:** [August 29, 2023, 1:24am UTC](https://forum.clockworkpi.com/t/were-still-using-apt-key-in-2023/10798/1 "2023-08-29T01:24:37Z")

</div>

Anybody else getting a ton of trusted.gpg errors running apt?

---

<div class="post-metadata">

**Author:** ![polymerwitch](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.clockworkpi.com/polymerwitch/32/6698_2.png) [@polymerwitch](https://forum.clockworkpi.com/u/polymerwitch)\
**Post date:** [August 29, 2023, 1:31am UTC](https://forum.clockworkpi.com/t/were-still-using-apt-key-in-2023/10798/2 "2023-08-29T01:31:55Z")

</div>

yeah, I was able to grab the needed keys from the ubuntu key server and then add them to /etc/apt/keyrings/ and update the sources files to reference them.

---

<div class="post-metadata">

**Author:** ![USFrozen](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.clockworkpi.com/usfrozen/32/7065_2.png) [@USFrozen](https://forum.clockworkpi.com/u/USFrozen)\
**Post date:** [August 29, 2023, 3:29am UTC](https://forum.clockworkpi.com/t/were-still-using-apt-key-in-2023/10798/3 "2023-08-29T03:29:44Z")

</div>

I haven’t had any APT gpg errors. The only APT related issue I’ve had so far was when updating temporarily broke my WiFi, but i was already expecting that from other peoples posts.

---

<div class="post-metadata">

**Author:** ![barry99705](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.clockworkpi.com/barry99705/32/6771_2.png) [@barry99705](https://forum.clockworkpi.com/u/barry99705)\
**Post date:** [August 29, 2023, 1:25pm UTC](https://forum.clockworkpi.com/t/were-still-using-apt-key-in-2023/10798/4 "2023-08-29T13:25:59Z")

</div>

cm4 or a06?

extra crap characters…

---

<div class="post-metadata">

**Author:** ![USFrozen](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.clockworkpi.com/usfrozen/32/7065_2.png) [@USFrozen](https://forum.clockworkpi.com/u/USFrozen)\
**Post date:** [August 29, 2023, 3:37pm UTC](https://forum.clockworkpi.com/t/were-still-using-apt-key-in-2023/10798/5 "2023-08-29T15:37:21Z")

</div>

I got the CM4 model, and im still using the default image that shipped with it while I tinker on a separate SD card.

This is unrelated to the topic, but I must say the WiFi on the CM4 model is unreliable AF and the Bluetooth is _terrible_. I am actually getting worse WiFi connection and more drops when telling it to use the external antenna using `dtparam=ant2` and unless I have the top back part of the uConsole pointed at my BT receiver i cant even use it for connecting a mouse and keyboard.

---

<div class="post-metadata">

**Author:** ![polymerwitch](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.clockworkpi.com/polymerwitch/32/6698_2.png) [@polymerwitch](https://forum.clockworkpi.com/u/polymerwitch)\
**Post date:** [August 29, 2023, 4:06pm UTC](https://forum.clockworkpi.com/t/were-still-using-apt-key-in-2023/10798/6 "2023-08-29T16:06:48Z")

</div>

I have the A06, and it had the key errors.

---

<div class="post-metadata">

**Author:** ![Qazax](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.clockworkpi.com/qazax/32/6664_2.png) [@Qazax](https://forum.clockworkpi.com/u/Qazax)\
**Post date:** [August 29, 2023, 4:11pm UTC](https://forum.clockworkpi.com/t/were-still-using-apt-key-in-2023/10798/7 "2023-08-29T16:11:59Z")

</div>

Could you walk me through how to do this please? I have attempted it and got nowhere. A06, on freshly imaged SD card I have tried in the command line and in the gui to import the keys but apt update still fails saying missing public key.

---

<div class="post-metadata">

**Author:** ![polymerwitch](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.clockworkpi.com/polymerwitch/32/6698_2.png) [@polymerwitch](https://forum.clockworkpi.com/u/polymerwitch)\
**Post date:** [August 29, 2023, 5:16pm UTC](https://forum.clockworkpi.com/t/were-still-using-apt-key-in-2023/10798/8 "2023-08-29T17:16:05Z")

</div>

Sure. First, copy the key ID from the error message. It will look something like: “648ACFD622F3D138”

Then grab that key:

```auto
gpg --keyserver hkps://keyserver.ubuntu.com --recv-keys KEYID

```

Next, export the key as a file:

```auto
gpg --export KEYID > REPONAME.gpg

```

Then copy it to the keyrings directory:

```auto
sudo cp REPONAME.gpg /etc/apt/keyrings/REPONAME.gpg

```

Then edit the appropriate apt sources file to reference the keys:

```auto
echo "deb [signed-by=/etc/apt/keyrings/REPONAME.gpg] https://somerepo.com/apt stable main" |
    sudo tee /etc/apt/sources.list.d/REPONAME.list

```

I just went in and edited the files so the URL and everything was correct  
Finally, delete the old keys from the trusted gpg db if any:

```auto
sudo apt-key del KEYID

```

---

<div class="post-metadata">

**Author:** ![barry99705](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.clockworkpi.com/barry99705/32/6771_2.png) [@barry99705](https://forum.clockworkpi.com/u/barry99705)\
**Post date:** [August 29, 2023, 7:57pm UTC](https://forum.clockworkpi.com/t/were-still-using-apt-key-in-2023/10798/9 "2023-08-29T19:57:48Z")

</div>

also doesn’t help the github cli cert is expired.

---

<div class="post-metadata">

**Author:** ![Qazax](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.clockworkpi.com/qazax/32/6664_2.png) [@Qazax](https://forum.clockworkpi.com/u/Qazax)\
**Post date:** [August 29, 2023, 7:58pm UTC](https://forum.clockworkpi.com/t/were-still-using-apt-key-in-2023/10798/10 "2023-08-29T19:58:34Z")

</div>

Thanks for this, I will try this out tonight.
