testcontainers / testcontainers/testcontainers-java
[Enhancement]: Publish the gpg coding signing keys used for maven central
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 8.7k
- Forks
- 1.9k
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 9
Description
Module
All
Proposal
For security purposes, it would be great if you were able to publish the gpg keys that are "valid" for use when signing artifacts uploaded to maven central.
Ideally, this would be published to https://www.testcontainers.org/
recent versions of testcontainers jvm artifacts are signed with this key:
https://keyserver.ubuntu.com/pks/lookup?search=2655176f748fd83725b4805ff2a01147d830c125&fingerprint=on&op=index
Some examples of publishing keys:
https://square.github.io/okhttp/security/security/#verifying-artifacts
https://github.com/eclipse/jetty.project/blob/jetty-10.0.x/KEYS.txt
https://downloads.apache.org/commons/KEYS
https://downloads.apache.org/logging/KEYS
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 by reviewing the documentation on testcontainers.org and the referenced signing-key fingerprint and examples from OkHttp and Apache. Done means publishing the valid GPG signing key information for Testcontainers JVM artifacts in a discoverable documentation location.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- documentation, release, security
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100