Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

x/website/internal/dl: expose whether a release is a security release or not in API #44925

Open
hyangah opened this issue Mar 10, 2021 · 2 comments
Open

x/website/internal/dl: expose whether a release is a security release or not in API #44925

hyangah opened this issue Mar 10, 2021 · 2 comments
Labels
FeatureRequest NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Milestone
Unreleased

Comments

@hyangah
Copy link
Contributor

hyangah commented Mar 10, 2021

Tools that watch golang.org/dl endpoint to learn about new releases may benefit from this extra information.
Not every user is eager to update as soon as the new point release is available. But if the patch includes critical or important security patches, users should take it more seriously.

Would be better if extra information like severity (#44918) can be included too.

According to @dmitshur: whether a release is a security one or not is available in an internal x/website package, but that isn't easily accessible externally.
@dmitshur
Copy link
Contributor

dmitshur commented Mar 10, 2021 •
edited

The internal package is golang.org/x/website/internal/history. See Release.Security.

@dmitshur dmitshur added FeatureRequest NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. labels Mar 10, 2021
@dmitshur dmitshur added this to the Unreleased milestone Mar 10, 2021
@dmitshur
Copy link
Contributor

The https://golang.org/design/draft-vulndb design draft may also be a relevant factor to consider here.

CC @golang/security, @golang/release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
FeatureRequest NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Projects
None yet
Milestone
Unreleased
Development

No branches or pull requests
2 participants
@dmitshur @hyangah