Closed rabernat closed 6 months ago
@rabernat I am still considering the above RE: frequency et al. We should dig out and follow industry best practise regarding this. @cisaacstern I agree, we should link to some documentation (preferably someone else's to save duplication of effort) around good password hygiene and how to make strong passwords. Preferably with a few horror stories to push the point home.
One challenge I see around secret rotation is the fact that encrypted secrets will get checked into the feedstocks once and potentially stay there for years! Should we expect receipe maintainers to periodically re-encrypt their credentials after we rotate keys? Or would it be okay to keep using the old keys to for those old secrets?
and potentially stay there for years!
This should only become relevant if the feedstock is re-run (i.e., if it's tagged with a new version), correct? In which case we could add a GitHub workflow to the feedstock template repository that checks if the gpg key used is up-to-date? This would require adding a field for gpg key to the meta.yaml
, I guess. (Which maybe isn't such a bad idea anyway?) I'm assuming here there is no way to recover a public key directly from an encrypted file
Just learned about https://github.com/mozilla/sops via @yuvipanda's tweet. Seems like another useful option to consider re: secret handling.
Yeah, sops is amazing and much more user friendly than gpg. Highly recommend. You can use gpg with it too if you like.
SOPS is 100% where its at. I have deployed this into production at a few places now.
closing as stale
This is a potential solution to handling of secrets in Pangeo Forge.