fix bore url and ngrok default

ariary · Sep 19, 2022 · 7189100 · 7189100
1 parent 0562d3f
commit 7189100
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 2 deletions.
diff --git a/README.md b/README.md
@@ -46,8 +46,10 @@ tmux
 Useful if target can't directly reach the attacker machine, but has internet access
 <br> On attacker machine, install <code>ngrok</code> or <code>bore</code> and launch your listener:
 <pre><code>
-./light-pty4all/socat-listener-behind-tunneling.sh --ngrok
+./light-pty4all/socat-listener-behind-tunneling.sh
 </code></pre>
+
+<i><b>N.B:</b></i> ngrok is more stable than bore for now
 </details>
 
 ### With docker (recommended)

diff --git a/light-pty4all/socat-listener-behind-tunneling.sh b/light-pty4all/socat-listener-behind-tunneling.sh
@@ -50,7 +50,7 @@ fi
 if [[ "$HELP" ]];
 then
  echo "Usage : $0 -p <socat_port>";
- echo -e "\t--ngrok to perform tunneling usi,ng ngrok instead of bore"
+ echo -e "\t--bore to perform tunneling using bore instead of ngrok"
  echo -e "\t-w/--windows if target is a winows machine"
  echo -e "\t-p/--lport for the socat listener local port"
  echo -e "\t--web-port for the gitar lcoal port"