# SAdoor winserver (1.1)
Commands |
Disable Run Command | Disable "single commands", i.e. SAdoor will ignore to run shell commands received within the payload of the command packet.
Disable ACCEPT Command | Disable passive mode. SAdoor will refuse to listen for connection to a local port (on the first IPv4 address of the selected interface) from the address received in the payload of the command packet.
Disable CONNECT Command | SAdoor will refuse to connect back to any client sending a connect-back request within the payload of the command packet.
Disable File Transfer | Disable file transfer, useful to prevent bypassing of a program that is run upon connect
NULLCommand | The command to run when the command packet does not contain command. Note that this is dangerous since only knowledge of the packets is required to run this command. Leave blank to disable
Run On Connect | The program/command to run when a connection is established
Settings |
Create PID File | Create file containing PID of SAdoor to prevent multiple SAdoor processes
Replay Protection | Enable protection against replay attacks. If someone manages to sniff the packets required to trigger SAdoor, it is not possible to run arbitrary commands since that requires knowledge about the key, but it is possible to re-run the sniffed command. If enabled, SAdoor will refuse to run any command received with a timestamp (seconds and micro seconds in GMT) less or equal to the previous one.
Resolve Hostnames | When loggin IP addresses, try to resolve the hostnames as well
Packet Timeout | Number of seconds that SAdoor will wait for the required packets after the first is received. When timed out, all the packets have to be sent again. Set to zero to disable, and make SAdoor wait forever
Log Level | Verbose level of log, set to zero to disable all logging. A level of 3 is probably enough for everybody not debugging
Network interface |
Enable Dynamic IPv4 | If you have a dynamic IPv4 address on the machine running SAdoor, you can set this to make SAdoor look for a change of address, and set the destination address of the awaiting packets accordingly
Edit Destination | The destination address to change in packets.txt if dynamic IPv4 is set. This marks the packets expected to go to the host running SAdoor, i.e. set the destiantion address of the packets that should go to the host running SAdoor to, lets say 255.255.255.255, and write that address in this field. When Sadoor starts, all the destiantion addresses set to 255.255.255.255 will be replaced with the first IPv4 address of the selected interface The address is also polled when SAdoor is running, in case of another address change
Promiscous Mode | Listen for packets in promiscuous mode. Note that the interface used could be in promiscuos mode for some other reason. If the awaiting packets is defined with promiscuous mode in mind, SAdoor can be triggered by packets going to a completely different host
Files |
Blowfish Key | Contains the 448 bit Blowfish key used by the clients for symmetric encryption of the data/command set in any command packet. Do not forget to generate a new SAdoor Database File when you generate a new key file.
SAdoor Database Entry | The file to write the information needed by the client to send commands. The generated file is not encrypted, so you need to transfer it in a secure channel to the client
Packet Configuration | The file containing the packets required to trigger SAdoor. The original file contains description of syntax and examples.