NVIDIA / NVIDIA/nvidia-container-toolkit
Expired APT Repository Key
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 4.6k
- Forks
- 592
- Avg merge
- 1d 33m
- Merged PRs (30d)
- 61
Description
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) <cudatools@nvidia.com>
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.
Contributor guide
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 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.
Assessment
- Tech stack
- debian
- Domain
- security
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100