.deb linux repo uses deprecated trusted.gpg
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
After installing the .deb version of keybase, running apt update includes the following warning:
W: http://prerelease.keybase.io/deb/dists/stable/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details.
Here's how to fix it:
sudo apt-key export 222B85B0F90BE2D24CFEB93F47484E50656D16C7 > keybase.asc
sudo mv keybase.asc /etc/apt/trusted.gpg.d/
sudo chown root:root /etc/apt/trusted.gpg.d/keybase.asc
sudo apt-key del 222B85B0F90BE2D24CFEB93F47484E50656D16C7
It would be good if the installer put the repo signing key in /etc/apt/trusted.gpg.d/ directly instead of using trusted.gpg.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the .deb installer logic that configures the Keybase APT repository and imports its signing key. Verify the resulting installation places the key under /etc/apt/trusted.gpg.d/ and that apt update no longer reports the legacy trusted.gpg warning.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux
- Domain
- release
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100