Home

git-age @main - refs - log -
https://git.jolheiser.com/git-age.git
git-crypt, but with age
-rw-r--r--
175 B
.git-age.yaml
drwxrwxrwx
42 B
.woodpecker/
drwxrwxrwx
366 B
cmd/
-rw-r--r--
39 B
.gitattributes
-rw-r--r--
10 B
.gitignore
-rw-r--r--
491 B
.goreleaser.yaml
-rw-r--r--
17 kB
LICENSE
-rw-r--r--
1.7 kB
README.md
drwxrwxrwx
70 B
secrets/
-rw-r--r--
1.5 kB
flake.lock
-rw-r--r--
1.2 kB
flake.nix
-rw-r--r--
971 B
go.mod
-rw-r--r--
7.7 kB
go.sum
-rw-r--r--
189 B
key.txt
-rw-r--r--
182 B
main.go
-rw-r--r--
282 B
man.go
-rw-r--r--
399 B
ssh
-rw-r--r--
89 B
ssh.pub

git-age

This is a Go port of git-agecrypt with some slight modifications.

Echoed from the original project:

Why should I use this?

Short answer: you probably shouldn't. Before considering this approach, take a look at SOPS and Hashicorp Vault if they are better suited for the problem at hand. They have a clear security advantage over git-age.

The one use-case where it makes sense to use git-age instead is when you want to keep some files secret on a (potentially public) git remote, but you need to have the plaintext in the local working tree because you cannot hook into the above tools for your workflow. Being lazy is not an excuse to use this software.

Adding git-age to a new repository

  1. Install git-age in your PATH
  2. git age init
  3. Add some identities
  1. Set up your config (example)
  2. Add your secrets to .gitattributes secret.txt diff=git-age filter=git-age
  3. Use git like normal.

Decrypting an existing repository

Similar to initial install, adding identities prior to init so that any encrypted files are decrypted during initialization.

  1. Install git-age in your PATH
  2. Clone the repository
  3. Add some identities
  1. git age init
  2. Use git like normal

License

This software was written based off of git-agecrypt.

MPL-2.0 (Original)