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

etcd-3.5/3.5.16-r1: cve remediation #33256

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

octo-sts[bot]
Copy link
Contributor

@octo-sts octo-sts bot commented Nov 5, 2024

Copy link
Contributor

github-actions bot commented Nov 5, 2024

Package etcd-3.5: Click to expand/collapse

Package etcd-3.5:
Modified: /usr/bin/etcd
Modified: /usr/bin/etcdctl
Modified: /usr/bin/etcdutl

Package etcd-3.5-bitnami-compat: Click to expand/collapse

Package etcd-3.5-bitnami-compat:
Modified: /opt/bitnami/.bitnami_components.json
Modified: /opt/bitnami/scripts/etcd/healthcheck.sh

Copy link
Contributor Author

octo-sts bot commented Nov 5, 2024

Gen AI suggestions to solve the build error:

Based on the build output, I notice the warning message:

WARN {"level":"warn","ts":"2024-11-05T07:50:20.661533Z","caller":"auth/store.go:1241","msg":"simple token is not cryptographically signed"}

This warning from etcd appears to be expected behavior and not actually causing a build failure. Looking through the logs, the package seems to build and test successfully:

  1. The etcd server starts up properly
  2. Key-value operations work as expected
  3. The test pipeline completes without errors
  4. The package builds successfully into an OCI image

The "simple token is not cryptographically signed" warning is just informational and doesn't impact functionality. It's warning that etcd is using simple token authentication which doesn't provide cryptographic signing - this is normal for basic testing/development scenarios.

If you want to remove this warning, you could:

  1. Configure authentication with TLS certificates
  2. Add the appropriate security configuration in the melange YAML
  3. Or simply ignore it as it's not impacting package functionality

Unless you have other specific build errors not shown in these logs, the package appears to be building correctly despite this warning message.

@octo-sts octo-sts bot added bincapz/pass bincapz/pass Bincapz (aka. malcontent) scan didn't detect any CRITICALs on the scanned packages. P1 This label indicates our scanning found High, Medium or Low CVEs for these packages. auto-approver-bot/checks-failed labels Nov 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
auto-approver-bot/checks-failed automated pr bincapz/pass bincapz/pass Bincapz (aka. malcontent) scan didn't detect any CRITICALs on the scanned packages. etcd-3.5/3.5.16-r1 GHSA-29wx-vh33-7x7r go/bump P1 This label indicates our scanning found High, Medium or Low CVEs for these packages. request-cve-remediation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants