Blackbox
Our great sponsors
liferay-portal | Blackbox | |
---|---|---|
4 | 7 | |
2,052 | 6,620 | |
0.4% | 0.4% | |
10.0 | 3.0 | |
about 23 hours ago | 23 days ago | |
Java | Go | |
GNU General Public License v3.0 or later | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
liferay-portal
-
No comments. Now what?
The concepts are complex; even I would be confused rereading these asserts. A comment could explain them. But this commit already clarified everything by moving these lines to a method and invoking it:
-
Zsh Plugins Commit TOP
liferay 🥇 🏃♂️ ⏳ - Adds scripts for liferay development.
- Top Companies Contributing to Open Source - 2011/2021
- Rövid és felületes kutatás a vakcinás oldalakról
Blackbox
-
Safely store secrets in Git using Blackbox
Blackbox is a great tool for securely storing secrets within a Git repository. It provides an easy-to-use PGP encryption system, which ensures that secrets are kept safe and secure. Furthermore, Blackbox can also be used in GitHub Actions as a secret repository, allowing developers to quickly load secrets into their pipelines. With its robust security and automated processes, Blackbox is an excellent tool for securely storing secrets within Git.
-
Blackbox - Secrets amongst your code
One of the major concerns amongst developers is how to store shared secrets. Storing secrets in a config file along with your source code is problematic as it can compromise privacy. Storing it outside without proper process or documentation can tend to be forgotten (not saying this is not good as using SAAS tools like Vault is the way to go). But in case you have a limited budget and limited capability, using GPG is the way to go. Here comes Blackbox.
-
We have this many ".env" files in a project at work. Is this normal? Is there a better way?
My preferred version is blackbox: https://github.com/StackExchange/blackbox
-
Zsh Plugins Commit TOP
blackbox 🥇 💼 - Stack Exchange's toolkit for storing keys/credentials securely in a git repository.
- Quick Ansible Vault question
-
How do you provision app secrets?
For Puppet i use blackbox
-
Looking for an interesting project to contribute
Interested in making GPG easier to use for encrypting secrets in Git? https://github.com/StackExchange/blackbox is being rewritten in Go and needs help testing, improving, ensuring compatibility, etc.
What are some alternatives?
awesome-zsh-plugins - A collection of ZSH frameworks, plugins, themes and tutorials.
zsh-autocomplete - 🤖 Real-time type-ahead completion for Zsh. Asynchronous find-as-you-type autocompletion.
zsh-syntax-highlighting - Fish shell like syntax highlighting for Zsh.
pfSense - Main repository for pfSense
ranger - A VIM-inspired filemanager for the console
lynis - Lynis - Security auditing tool for Linux, macOS, and UNIX-based systems. Assists with compliance testing (HIPAA/ISO27001/PCI DSS) and system hardening. Agentless, and installation optional.
Vim - The official Vim repository
SpamAssassin - Read-only mirror of Apache SpamAssassin. Submit patches to https://bz.apache.org/SpamAssassin/. Do not send pull requests
zsh-autosuggestions - Fish-like autosuggestions for zsh
Wazuh - Wazuh - The Open Source Security Platform. Unified XDR and SIEM protection for endpoints and cloud workloads.
z - z - jump around
fwknop - Single Packet Authorization > Port Knocking