Expired APT Repository Key

Open
#650 6 comments 3 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
45/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Stale
Tech stack
debian
Domain
security

Research direction

Start with the Container Toolkit installation guide and the key served by https://nvidia.github.io/libnvidia-container/gpgkey; verify how the repository setup obtains and uses that key. Done means the distributed signing key is valid and Debian APT accepts packages from the Container Toolkit Repository without a signature or expired-key error.

Written by the indexing model from the issue text.

Description

lifecycle/frozen needs-triage package-management

As I tried to setup the Container Toolkit Repository (see https://docs.nvidia.com/datacenter/cloud-native/container-toolkit/latest/install-guide.html) on a Debian system, I got errors with the APT package manager, due to no accepted signature/public key. When checking the key, it turns out, that the key is expired.

$ curl -fsSL https://nvidia.github.io/libnvidia-container/gpgkey | gpg                                                                                                                                                    

gpg: WARNING: no command supplied.  Trying to guess what you mean ...
pub   rsa4096 2017-09-28 [SCE]
      C95B321B61E88C1809C4F759DDCAE044F796ECB0
uid           NVIDIA CORPORATION (Open Source Projects) <[email protected]>
sub   rsa2048 2019-09-18 [S] [expired: 2021-06-16]

It would be great if you could update the key expiry date and distribute the than valid key.

Dominant language
Go
Stars
4.6k
Forks
609
Avg merge
3d 12h
Merged PRs (30d)
36

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from NVIDIA/nvidia-container-toolkit

All issues in NVIDIA/nvidia-container-toolkit

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.