nccgroup / thetick Goto Github PK

Great tool you have. Still finding my way round it.
A few issues i think can improve user experience.I found the Readme to be a bit high level especially for guys not very familiar with compiling files.
This are some of my suggestions.
For make clean && make to work, users must be in the src folder. Once the command has run to completion, a new folder bin will be created. This folder contains the backdoor that you will put on the target system.
After running the ./ticksvc ip.here porthere. On the control machine, type bots. This will show a listing of all bots. To connect to a bot, type use 0 where 0 is the boot number.

The binary which is used on target machine is automatically compiled depend on the user's machine arch, I tried to play with the make file by changing cppflags and lddflags but no lock, I had to compile it in a 32bit machine to get the 32bit bin.

Hello!!
I was looking at this awesome project, but I noticed there is no guide on how to compile a binary for a different architecture, tried reading the printer compiling bit but I am still confused.

So could you kindly provide some basic requirements required to build for different architectures, like for example a router ...

Regards,

gr00t

the func in parser.h is void parser_begin_response(Parser *parser, uint8_t status, uint16_t length);
but used as parser_begin_response(Parser *parser, uint8_t status, uint32_t length); in file.c
When the file is too large, it will cause integer overflow, resulting in abnormal pull function