pkgsrc.se | The NetBSD package collection
./security/git-secret, Git subcommand to store your private data inside a git repository
[
CVSweb ] [
Homepage ] [
RSS ] [
Required by ] [
Add to tracker ]
Branch: CURRENT, Version: 0.5.0nb1, Package name: git-secret-0.5.0nb1, Maintainer: pkgsrc-users
git-secret is a bash tool which stores private data inside a git repo.
git-secret encrypts files with permitted users' public keys, allowing users you
trust to access encrypted data using pgp and their secret keys.
With git-secret, changes to access rights are simplified, and private-public
key issues are handled for you.
When someone's permission is revoked, secrets do not need to be changed with
git-secret - just remove their key from the repo's keyring using git secret
removeperson their@email.com, re-encrypt the files, and they won't be able to
decrypt secrets anymore. If you think the user might have copied the secrets or
keys when they had access, then you should also change the secrets.
Master sites:
Filesize: 834.47 KB
Version history: (Expand)
- (2026-01-28) Updated to version: git-secret-0.5.0nb1
- (2025-10-24) Package has been reborn
- (2025-10-24) Package deleted from pkgsrc
- (2025-07-15) Package has been reborn
- (2025-07-15) Package deleted from pkgsrc
- (2025-01-22) Package added to pkgsrc.se, version git-secret-0.5.0 (created)
CVS history: (Expand)
| 2026-01-29 11:03:12 by Thomas Klausner | Files touched by this commit (8) |
Log message: *: allow gnupg2 version 2.4.9nb2 for the renamed binaries |
| 2026-01-28 11:48:48 by Thomas Klausner | Files touched by this commit (1) |
Log message: git-secret: gnupg2 binary now gpg Remove SUBST*, bump PKGREVISION. |
| 2025-01-22 10:25:18 by Adam Ciarcinski | Files touched by this commit (4) |
Log message: git-secret: added version 0.5.0 git-secret is a bash tool which stores private data inside a git repo. git-secret encrypts files with permitted users' public keys, allowing users you trust to access encrypted data using pgp and their secret keys. With git-secret, changes to access rights are simplified, and private-public key issues are handled for you. When someone's permission is revoked, secrets do not need to be changed with git-secret - just remove their key from the repo's keyring using git secret removeperson their@email.com, re-encrypt the files, and they won't be able to decrypt secrets anymore. If you think the user might have copied the secrets or keys when they had access, then you should also change the secrets. |