When comparing StackExchange Blackbox vs git-secret, the Slant community recommends git-secret for most people. In the question“What are the best tools for storing secrets with Git?” git-secret is ranked 1st while StackExchange Blackbox is ranked 2nd. The most important reason people chose git-secret is:
Once the user has its GPG RSA Key-pair ready, running `git secret init` command will create `.gitsecret/` folder, where the secret files will need to be added with the command `git secret add <filenames...>`, finally using `git secret hide`, will encrypt the files using the keys added with `git secret tell` command, then, they will be ready to be committed.
Ranked in these QuestionsQuestion Ranking
Pros
Pro Easily share secrets with other team members
Since the secrets file is stored in the remote VCS server, anyone that has access to it (team members) also have access to the secrets file.
Pro Free and open source
StackExchange Blackbox is free and open source. It's released under the MIT license and its source code is freely available on GitHub.
Pro Uses a VCS repo to store the secrets
SE Blackbox works with Git, Mercurial, Subversion and Perforce to store encrypted secrets file in a repository. Files are automatically encrypted and decrypted using GNU Privacy Guard.
Pro Easy and straightforward usage
Once the user has its GPG RSA Key-pair ready, running git secret init
command will create .gitsecret/
folder, where the secret files will need to be added with the command git secret add <filenames...>
, finally using git secret hide
, will encrypt the files using the keys added with git secret tell
command, then, they will be ready to be committed.
Pro Built-in access management
Can revoke or add keys to allow or deny access to users without needing to change your keys or passphrase.
Pro Keeps track of encrypted files
git-secret encrypts files and stores them inside the repo, allowing you to keep track for every commit.
Cons
