The sniffer has basic features like filter, decode, replay, parse The new raw socket implementation of Windows2000 (driverless),Ī NDIS protocol (needs to be installed, no reboot). The packet sniffer can work on all Windows versions using either : This can be used after the IO has been manipulated.IP Sniffer is a suite of IP Tools built around a packet sniffer. Echo the IO back to the respective application.
Gives the possibility to add in a fake IO line. They block the input/output for one line only. These only take effect if the respective global blockingInput/blockingOutput are set to false. This can replace a string in the IO with a different string. These can evaluate if the IO contains a certain string and then execute actions. if, elseIf and else conditional structures. To manipulate the IO the following possibilities are supported: It also allows blocking the input or output and manipulating the input and output. It allows you to set the location of the log file and the application file. To get a good idea of the possibilities you might want to check out the ConsoleSnifferExampleConfig.xml file. The real power of ConsoleSniffer comes to show when a configuration file is used. application=FILE The called application. log=FILE Append all the command line IO to a file. overwriteConfig Turn off the default overriding of command line arguments by the config file. generateConfig Generate an example configuration file that uses the passed command line arguments. When passing command line arguments that are also defined in the config file, the command line arguments will be overriden by default. config=FILE Use a configuration file to configure ConsoleSniffer. blockOutput=BOOL Prevent the called application's output from being sent through to the calling application.
blockInput=BOOL Prevent the calling application's input from being sent through to the called application.
help Display a notice with all possible arguments. Next I'll give you an overview of the possible arguments: snifferArgsBegin -application=D:/someapplication.exe -log=D:/logfile.txt -snifferArgsEnd) As ConsoleSniffer is designed to pass through arguments to the called program all arguments meant for it should be enclosed within -snifferArgsBegin and -snifferArgsEnd. In that case I'll provide you with some information to make your life a bit easier.įirst and foremost are the command line arguments. If you've managed to read this far, you're probably interested in using ConsoleSniffer. ConsoleSniffer will then call the desired program itself and monitor all communications.ĬonsoleSniffer WILL NOT monitor interactions between programs it has no correlation to. This will only work if you can get the calling program to call ConsoleSniffer in stead of the called program. ConsoleSniffer is a program that monitors (and alters) the console input/output action between two programs.
0 kommentar(er)
