Shouldn’t Forgejo private repositories be encrypted?
-
Wouldn’t it make sense for Forgejo to encrypt private repositories so users could safely include sensitive data like logs, histories, or even login configs?
For example, I currently exclude things like my Zsh history in
.gitignore
in my dotfiles repo. If private repos were encrypted, I could just commit everything and sync my full setup between machines without relying on Syncthing or other tools.Is there any plan or reason why Forgejo doesn’t encrypt private repos this way?
-
Wouldn’t it make sense for Forgejo to encrypt private repositories so users could safely include sensitive data like logs, histories, or even login configs?
For example, I currently exclude things like my Zsh history in
.gitignore
in my dotfiles repo. If private repos were encrypted, I could just commit everything and sync my full setup between machines without relying on Syncthing or other tools.Is there any plan or reason why Forgejo doesn’t encrypt private repos this way?
No? It doesn't seem to be a use case they target.
If you want to use git to store sensitive data, you should encrypt it before committing / pushing it.
-
No? It doesn't seem to be a use case they target.
If you want to use git to store sensitive data, you should encrypt it before committing / pushing it.
No? It doesn’t seem to be a use case they target.
The problem is that making a repository private makes users think their data can't be seen so they may upload that kind of information.
If you want to use git to store sensitive data, you should encrypt it before committing / pushing it.
I'll look into that.