Skip to content

Commit 91a18f0

Browse files
committed
Add post about importing tails repository key
1 parent 3336dc2 commit 91a18f0

File tree

1 file changed

+50
-0
lines changed

1 file changed

+50
-0
lines changed
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,50 @@
1+
---
2+
vim: tw=79:ts=2:sw=2:ai:si:et
3+
title: Import the tails Debian repository key
4+
description: >-
5+
The import of the tails Debian repository key failed with '... but contains
6+
no user ID - skipped'. This is due to keys.openpgp.org stripping all ID
7+
information.
8+
category:
9+
- planet-debian
10+
- debian
11+
tags:
12+
- gnupg
13+
- tails
14+
- repository
15+
- apt-secure
16+
- openpgp
17+
---
18+
19+
I recently had to deal with [tails] to create a [custom image]. I needed to
20+
[add] the Tails repository to my system in order to build it. But `apt` started
21+
throwing errors:
22+
23+
```console
24+
$ sudo apt-get update
25+
[..]
26+
W: GPG error: http://deb.tails.boum.org builder-bullseye InRelease:
27+
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY C7988EA7A358D82E
28+
```
29+
30+
Trying to import the key failed too due to
31+
32+
```console
33+
$ gpg --recv-keys C7988EA7A358D82E
34+
gpg: key C7988EA7A358D82E: new key but contains no user ID - skipped
35+
gpg: Total number processed: 1
36+
gpg: w/o user IDs: 1
37+
```
38+
39+
Then I remembered that my default keyserver `hkp://keys.openpgp.org` [strips]
40+
the identity information. I finally ended up importing the key from the old SKS
41+
keyservers using `apt-key`:
42+
43+
```console
44+
$ sudo apt-key adv --keyserver hkps.pool.sks-keyservers.net --allow-non-selfsigned-uid --recv-keys C7988EA7A358D82E
45+
```
46+
47+
[tails]: https://tails.boum.org/
48+
[custom image]: https://tails.boum.org/contribute/how/code/HACKING/
49+
[add]: https://tails.boum.org/contribute/build/
50+
[strips]: https://keys.openpgp.org/about

0 commit comments

Comments
 (0)