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

Upgrade go. #596

Open
wants to merge 3 commits into
base: main
Choose a base branch
from
Open

Upgrade go. #596

wants to merge 3 commits into from

Conversation

Tang8330
Copy link

@Tang8330 Tang8330 commented Oct 21, 2024

Upgrading Go to address CVEs stemming from stdlib

@alerque
Copy link
Contributor

alerque commented Oct 21, 2024

Do the CVEs really affect this app or do they just happen to exist in an unrelated/unused API surface in Go?

@Tang8330
Copy link
Author

image

Not sure, but given it's just a Go upgrade, I don't see why we wouldn't just address them.

@alerque
Copy link
Contributor

alerque commented Oct 21, 2024

At least one of those has already been brought up here: #409 (comment).

The more general point of "why not just bump" is also addressed in places like here: #458 (comment).

@Tang8330
Copy link
Author

I understand the position of not wanting to bump for the sake of bumping a CVE that may not actually impact age, thus generating busywork.

However, how do you plan to actually tackle triaging to ensure that appropriate CVEs are being addressed and providing a rationale for why particular CVEs that have been flagged are being purposefully ignored?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants