envoyproxy/envoy

Signed releases

Open

#14,076 opened on Nov 18, 2020

View on GitHub
 (18 comments) (2 reactions) (0 assignees)C++ (5,373 forks)batch import
area/buildarea/securityenhancementhelp wanted

Repository metrics

Stars
 (27,997 stars)
PR merge metrics
 (Avg merge 8d) (378 merged PRs in 30d)

Description

Running https://github.com/ossf/scorecard against https://github.com/envoyproxy/envoy gives generally a high score, but we are missing signed releases/tags. The idea is to attach a GPG ASCII signature to the release/tag artifacts.

Arguably the benefit is marginal if we trust GitHub security (how many Envoy consumers will check this signature?), but this seems a reasonable defense-in-depth best practice to follow.

Contributor guide

Research direction
Examine the existing release workflow and CI pipeline, then implement GPG signing for release artifacts and tags.
Tech stack
None
Domain
securityrelease
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitGPGGitHub Releases
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65