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?

  • Joe@discuss.tchncs.de
    link
    fedilink
    arrow-up
    19
    ·
    14 hours ago

    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.

    • Davy Jones@lemmy.dbzer0.comOP
      link
      fedilink
      arrow-up
      8
      arrow-down
      3
      ·
      edit-2
      14 hours ago

      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.

      • illusionist@lemmy.zip
        link
        fedilink
        arrow-up
        7
        ·
        edit-2
        13 hours ago

        Usually you don’t accidentally open a git repo and set up a ssh key and push your own credentials to a foreign repo. Usually that involes reading a manual. If those tutorial don’t cover keys, then the tutorials need to be improved. imo

        Moreover, maybe a global password save would be good

      • TomAwezome@lemmy.world
        link
        fedilink
        arrow-up
        2
        ·
        11 hours ago

        Generally if you want to combine full encryption with version control, your best bet would be instead to not use something like Forgejo, and instead do something like init a local git repo, commit like usual, then set up scripting that will tar.gz archive the entire repo, PGP encrypt the archive, and then upload that to a cloud provider’s file storage. That way, it’s got privacy (the archive is encrypted), it’s got version control (once decrypted and decompressed it goes back to being a folder with a git repo in it), and it’s backed up (via cloud file storage provider).