2 ms·
How is it a risk to the attacker? The attacker isn't presenting a shell on his server, the client is the one presenting the shell. You could just as well post
by jstanley 13y ago
How is it a risk to the attacker? The attacker isn't presenting a shell on his server, the client is the one presenting the shell.
You could just as well post the IP address somewhere and connect later, but then you have to worry about escaping NAT.
I don't really know what resources would help, possibly the netcat man page? http://linux.die.net/man/1/nc http://linux.die.net/man/1/nc
- bigd 13y agosince you are statically sharing the server details... Isn't this as leaving your id card on the crime scene? anyway, for who might be interested, the technical term is "reverse shell" (the one in the article) or "bind shell" (the one I wanted).