You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is there any chance of adding the possibility to store encrypted secrets in for example mysql/mariadb/postgres?
The fact that this only can be stored in cache backends like memcached/redis is kind of a bummer for specific k8s/openshift environments where you want to be able to drain nodes/delete pods on the fly.
Keep up the good work! You guys are killing it. :)
The text was updated successfully, but these errors were encountered:
The reason for not having any SQL storage at this point is that those do not support TTLs and the project would have to rely on a vacuum feature implemented in the yopass server. I've also wanted the secrets stored with yopass to be ephemeral and for "short" transactions only and not writing any data to disk has felt safer in case it turns out that tomorrow the encryption strategy is broken or incorrect for some reason.
Redis actually provide some sort of persistence so in case you want to rely on a persistence volume for data across redeploys of the database checkout https://redis.io/topics/persistence
For the deployments I've worked with in the past I separate the service and the database allowing for separate deployments, the memcache service almost never restart and I'm okay with that happening in rare cases.
Is there any chance of adding the possibility to store encrypted secrets in for example mysql/mariadb/postgres?
The fact that this only can be stored in cache backends like memcached/redis is kind of a bummer for specific k8s/openshift environments where you want to be able to drain nodes/delete pods on the fly.
Keep up the good work! You guys are killing it. :)
The text was updated successfully, but these errors were encountered: