Blackbox
fish-shell
Blackbox | fish-shell | |
---|---|---|
7 | 320 | |
6,624 | 24,593 | |
0.1% | 0.9% | |
3.0 | 9.9 | |
30 days ago | 1 day ago | |
Go | Rust | |
MIT License | GNU General Public License v3.0 or later |
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.
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.
fish-shell
-
FAQ on the xz-utils backdoor β via a project dev
Reminds of the note at the bottom of Fish's releases. It's there because the build system cannot determine the current version for some reason. Hopefully that will go away now that they have switched to a different language / build system. The custom tarball is used by Arch Linux at the very least.
https://github.com/fish-shell/fish-shell/releases/tag/3.7.1
https://github.com/fish-shell/fish-shell/issues/7772#issueco...
https://gitlab.archlinux.org/archlinux/packaging/packages/fi...
- Oh My Zsh
- Proposal for porting fish-shell from C++ to Rust
-
Converting the Kernel to C++
A recent practical example of the former: the fish shell re-wrote incrementally from C++ to Rust, and is almost finished https://github.com/fish-shell/fish-shell/discussions/10123
An example of the latter: c2rust, which is a work in progress but is very impressive https://github.com/immunant/c2rust
It currently translates into unsafe Rust, but the strategy is to separate the "compile C to unsafe Rust" steps and the "compile unsafe Rust to safe Rust" steps. As I see it, as it makes the overall task simpler, allows for more user freedom, and makes the latter potentially useful even for non-transpiled code. https://immunant.com/blog/2023/03/lifting/
-
Fish shell 3.7.0: last release branch before the full Rust rewrite
And this discussion from November has an update on the progress: https://github.com/fish-shell/fish-shell/discussions/10123
-
Day 5 - More or less...
We're using bash as our terminal shell for now (it is standard in many distros) but it is not the only one out there. If you want to test out zsh, fish or oh-my-zsh, you will see that there are a few differences and the features are usually the main differentiator. Try that, poke around.
-
Fish β Update on the Rust Port
They have a variety of reasons to move to rust, as outlined in their original rust discussion[1]. Mostly around finding other contributors, and adding an async/parallel mode they're comfortable with.
[1] https://github.com/fish-shell/fish-shell/pull/9512
- Devuan γ’γγγ°γ¬γΌγ: 4 γγ 5 Daedalus γΈ
What are some alternatives?
zsh-autocomplete - π€ Real-time type-ahead completion for Zsh. Asynchronous find-as-you-type autocompletion.
powerlevel10k - A Zsh theme
pfSense - Main repository for pfSense
starship - βποΈ The minimal, blazing-fast, and infinitely customizable prompt for any shell!
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.
nushell - A new type of shell
SpamAssassin - Read-only mirror of Apache SpamAssassin. Submit patches to https://bz.apache.org/SpamAssassin/. Do not send pull requests
oh-my-fish - The Fish Shell Framework
Wazuh - Wazuh - The Open Source Security Platform. Unified XDR and SIEM protection for endpoints and cloud workloads.
xonsh - :shell: Python-powered, cross-platform, Unix-gazing shell.
fwknop - Single Packet Authorization > Port Knocking
tokyonight.nvim - π A clean, dark Neovim theme written in Lua, with support for lsp, treesitter and lots of plugins. Includes additional themes for Kitty, Alacritty, iTerm and Fish.