| This property is allocated | ||||||||||||||||||||||||
|
|
To write your own plugin for Back Orifice, simply create a DLL with functions in the form: char *YourFunc(int *active, char *args) The Plugin execute command allows you to specify a dll and function name in the form "dll:_Function". The rest of the paramaters are passed to your function in the args paramater. The only thing your application is responsible for is to monitor the int that active is pointing to. If that value becomes 0, the user has requested that this plugin exit and your function should return as quickly as possible after shutting down whatever is necessary. Your program can either return NULL, or it can return a pointer to a static buffer containing a text message that will be displayed to the user. The DLL will not be unloaded until after the text has been copied from that buffer. That's all there is to it. | |||||||||||||||||||||||
|
|
To upgrade a running copy of Back Orifice remotely, simply upload the new version of the server to the remote host, and use the Process spawn command to execute it. When run, the server will automatically kill any programs running as the file it intends to install itself as, install itself over the old version, run itself from its installed position, and delete the updated exe you just ran. Before installation, several aspects of the server can be configured. The filename that Back Orifice installs itself as, the port the server listens on, and the password used for encryption can all be configured using the boconf.exe utility. If the server is not configured, it defaults to listening on port 31337, using no password for encryption (packets are still encrypted), and installing itself as " .exe" (space dot exe). The client communicates to the server via encrypted UDP packets. For successful communication, the client needs to send to the same port the server is listening on, and the client password must match the encryption password server was configured with. The port the client sends its packets from can be set using the -p option with both the gui and text clients. If packets are being filtered or a firewall is in place, it may be necessary to send from a specific port that will not be filtered or blocked. Since UDP communication is connectionless, the packets might be blocked either on their way to the server or the return packets might be blocked on their way back to the client. | |||||||||||||||||||||||
|
|
|
Favourite links
|
|
| ||||||||||||||||||||
|
This page has been visited
|