-
As things currently stand each users alertmanager configuration is stored as a plaintext JSON byte object in a postgres table. Since alertmanager configs contain api keys and passwords functionality s…
-
I installed this recently, great tool. But can't find where the secrets are being stored, on my installation (Ubuntu 20.04) the directory `~/.2fa `does not exist!
-
Hey I would like to test out your work. It looks like a great base for a project I want to create. I was wondering how should the the secrets be store in github?
Should they be something like
SEC…
-
I'm opening this issue to document/get my head around the current approach to security in resuming a session in solid-oidc.
My understanding of the current situation is:
- it is common practice to…
-
Secrets should be storable in existing Kubernetes secrets so that they don't have to be passed directly to helm. This is possible for certificates, but not for:
* External DB password
* SMTP user pa…
gansb updated
2 years ago
-
**Is your feature request related to a problem? Please describe.**
I'm currently using External Secrets to template secrets for PostgreSQL connections:
Format
```
postgres://{{ .username }}:{{…
-
These keys made it into the remote repository and should be considered compromised.
https://github.com/sitecues/sitecues-nomnom-clean/blob/master/nomnom-clean.sh#L1
Git does not enforce any kind of …
-
How do I force helm to treat a secret as a string? We have the following "secrets.yaml" file:
```
---
apiVersion: v1
kind: Secret
metadata:
name: {{ default .Values.global.name }}
type: Opa…
-
I have a whole bunch of secrets stored in the `/run/secrets/scripts` directory. I want to put the directory `/run/secrets/scripts` into a non-root user's $PATH, but since that user doesn't have permis…
-
Currently, the metadata for all OIDC clients is a single monolithic file in JSON format stored on each IdP server. There are several problems with this situation:
1. Any (necessarily manual) edit to …