-
Notifications
You must be signed in to change notification settings - Fork 760
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
Database password is stored in Configmap as clear text #111
Comments
this is critical security issue, on our cluster, all pod's stdout get collected and sent to a elasticsearch cluster which means the value of our password get indexed. so even if the value would be stored these kind of logs will get posted.
|
@darend Thanks for your feedback, we'll fix it. |
@darend The issue of password leaking is tracked by goharbor/harbor#7510. |
@ywk253100 Thanks. That issue tracks logging of passwords, there is still the issue that the password is stored in a ConfigMap vs Secret |
Fixes goharbor#111, store the database password of clair and notary in secret instead of configmap Signed-off-by: Wenkai Yin <[email protected]>
Fixes goharbor#111, store the database password of clair and notary in secret instead of configmap Signed-off-by: Wenkai Yin <[email protected]>
Fixes goharbor#111, store the database password of clair and notary in secret instead of configmap Signed-off-by: Wenkai Yin <[email protected]>
The password for the clair and notary databases are stored in a Configmap as clear text. It should be stored as Secret for security.
A template is used to construct the postgres URL with the password:
harbor-helm/templates/_helpers.tpl
Lines 133 to 143 in c263ec9
Its then used in the configmaps:
harbor-helm/templates/clair/clair-cm.yaml
Line 15 in c263ec9
harbor-helm/templates/notary/notary-cm.yaml
Line 35 in c263ec9
harbor-helm/templates/notary/notary-cm.yaml
Line 59 in c263ec9
The text was updated successfully, but these errors were encountered: