How do I save myself from myself?
* rm -rf *
* git reset --hard
Before hitting the enter key?
* kubectl delete ns
Stop! you are going to delete a lot of resources
* And many more!
Do you want to learn from other people mistakes?
shellfirm
will intercept any risky patterns (defined by default or any other user custom additions) it will immediately prompt a small challenge that will double verify your action, think of a captcha for your terminal.
```bash $ rm -rf /
Solve the challenge: 8 + 0 = ? (^C to cancel) ```
shellfirm
will evaluate all the shell commands behind the scenes.
If a risky pattern is detected, you will immediately get a prompt with the relevant warning for verification you command.
1) Install via brew
bash
brew tap kaplanelad/tap && brew install shellfirm
OR download the binary file from releases page, unzip the file and move to /usr/local/bin
folder.
2) select shell type:
Download zsh plugin:
bash
curl https://raw.githubusercontent.com/kaplanelad/shellfirm/main/shellfirm.plugin.zsh --create-dirs -o ${ZSH_CUSTOM:-~/.oh-my-zsh/custom}/plugins/shellfirm/shellfirm.plugin.zsh
Add shellfirm
as part of the list of Oh My Zsh plugins when Zsh is loaded(inside ~/.zshrc):
bash
plugins=(... shellfirm)
$ mkdir /tmp/shellfirm
$ cd /tmp/shellfirm
$ git reset --hard
You should expect to get shellfirm
prompt challenge.
If you didn't got the prompt challenge:
1. Make sure the shellfirm --version
return you valid response.
2. Make sure that you download the Zsh plugin and load as part of Oh My Zsh plugins.
We have defined a baseline of risky groups command that will be enabled by default ,these risky group commands might be destructive.
| Group | Enabled By Default |
| --- | --- |
| base | true
|
| git | true
|
| fs | true
|
| fs-strict | false
shellfirm config update --check-group fs-strict
|
| kubernetes | false
shellfirm config update --check-group kubernetes
|
| kubernetes-strict | false
shellfirm config update --check-group kubernetes-strict
|
shellfirm
creates by default a configuration file at ~/.shellfirm/config.yaml
. Make sure that you only edit enable
field (in case you want to disable a specific check), all the rest fields are managed by shellfirm
command (shellfirm config --help
).
```yaml challenge: Math # Math, Enter, Yes
includes: - base - fs - git
checks: - test: git reset method: Contains enable: true description: "This command going to reset all your local changes." from: git challenge: Default - test: "rm.+(-r|-f|-rf|-fr)" method: Regex enable: true description: "You are going to delete everything in the path." from: fs challenge: Default - test: ">.+/dev/sda" method: Regex enable: true description: "Writing the data directly to the hard disk drive and damaging your file system." from: fs challenge: Default - test: "mv+./dev/null" method: Regex enable: true description: "The files will be discarded and destroyed." from: fs challenge: Default ```
:information_source: To define custom checks that are not part of shillfirm
baseline, add new checks to the config.yaml with the following field: from: custom
.
yaml
- test: "command to check"
method: Regex
enable: true
description: "Example of custom check."
from: custom
challenge: Default
:information_source: To define different challenge for a checks you can change the field challenge: Default
with a different check.
bash
$ shellfirm config update --check-group {risky-command-group-a} {risky-command-group-b}
bash
$ shellfirm config update --check-group {group} {group} --remove
Edit the configuration file in ~/.shellfirm/config.yaml
and change the check to enable:false
.
Currently we support 3 different challenges when a risky command is intercepted:
* Math
- Default challenge which requires you to solve a math question.
* Enter
- Required only to press Enter
to continue.
* Yes
- Required typing yes
to continue.
You can change the default challenge by running the command:
bash
$ shellfirm config challenge --challenge Math
At any time you can cancel risky command by hitting ^C
shellfirm
:
bash
$ brew upgrade shellfirm
Thank you for your interest in contributing! Please refer to contribution guidelines for guidance.