feat: added gosec G101

[kadern0]

Signed-off-by: Pablo Caderno kaderno@gmail.com

Description

As described on #3545, added gosec G101

[openshift-ci]

Hi @kadern0. Thanks for your PR.

I'm waiting for a stackrox member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[janisz]

/ok-to-test

[0x656b694d]

Hi @kadern0. Thank you for addressing this. Now, please help us to fix the false positive G101 alerts:

pkg/satoken/paths.go:6:2: G101: Potential hardcoded credentials (gosec)
	ServiceAccountTokenDir = `/run/secrets/kubernetes.io/serviceaccount`
	^
pkg/auth/htpasswd/reader_test.go:16:8: G101: Potential hardcoded credentials (gosec)
	const htpasswd = `user:$2y$05$zOuqmZyoE82NGG4iitj91OrOQBoCrn0d/LiyHL833EvBzm0Wyy85.
other:$2y$05$b9mSdCSh6OnHhRDG/DAXee8USMpWYMK5XZcBZwFjQnCD5xQOu.F8y
admin:$2y$05$l.sGXGtYVWaoywFO06gDZeIHME8BFKWRuNv5PG4RLGUk0Yq/M4c86`
operator/pkg/proxy/status_condition.go:11:2: G101: Potential hardcoded credentials (gosec)
	SecretReconcileErrorReason = `ProxyConfigSecretReconcileError`
	^

[roxbot]

Images are ready for the commit at 06d6b71.

To use with deploy scripts, first export MAIN_IMAGE_TAG=3.72.x-421-g06d6b71bb8.

[janisz]

@kadern0 Two files are not passing gosec check

[janisz]

I think we can issue //nolint:gosec:G101 and they are false positives

[janisz]

style checks are failing

[gitguardian]

⚠️ GitGuardian has uncovered 2 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	Secret	Commit	Filename
-	Generic High Entropy Secret	06d6b71	central/metadata/service/service_impl_test.go	View secret
-	Generic High Entropy Secret	06d6b71	sensor/common/centralclient/client_test.go	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

<sup>🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

Our GitHub checks need improvements? Share your feedbacks!</sup>