tensorflow / tensorflow/serving
gpg key expired
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 6.4k
- Forks
- 2.2k
- PR merge metrics
- No merged PRs in 30d
Description
The GPG key for the APT repo expired, see: curl -so - https://storage.googleapis.com/tensorflow-serving-apt/tensorflow-serving.release.pub.gpg | gpg - returns:
pub rsa4096 2017-07-13 [SC] [expired: 2026-08-18]
916E2B2FEBC274930BACA9D9544B7F63BF9E4D5F
uid Tensorflow Serving Developer (Tensorflow Serving APT repository key) <tensorflow-serving-dev@googlegroups.com>
sub rsa4096 2017-07-13 [E] [expired: 2026-08-18]
This has been a recurring issue since 2019, please seriously consider renewing the key proactively or automating it.
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 published key at storage.googleapis.com/tensorflow-serving-apt/tensorflow-serving.release.pub.gpg and run the curl and gpg command from the issue to confirm its expiry. Determine whether the intended fix is renewal, proactive renewal, or automation; done means the APT repository key is valid and the recurring expiration risk is addressed.
Written by the indexing model from the issue text.
Assessment
- Domain
- release, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100