- Add concept of "master keypairs" or trusted "commanders" - people issuing commands.
- "server keypairs" or "trusted relay keypairs" are the C&C server keys that the client will trust. The idea here is to have one keypair for every trusted server, but not to actually trust the servers themselves for commands, but the person sending the commands.
- Build a framework for hiding file templates better (i.e. autostart file)
- Randomly generate the XOR keys for everything to make pattern generation harder.
- Implement a compiler in the server to randomize some things within every single build of the executable in order to make things more confusing
- Add the llvm obfuscation work in for modules
- Implement the rest of the events
- Add ping/pong in server/client
- Add tor config options to CTormInfo
- Override the
start_write_to_filefunctions in tor to write to internal configs instead. The problem with these functions is that they will write to normal files like (cached-microdescriptors.new) which are upwards of 2mb. We don't know the size before we start writing, though. So there'll be some awkward solution like writing to a temporary file and when the file is closed, serializing it into the storage and deleting the temp file.
Possible bugs:
- The module instances use CModule pointers to hold state. Make sure these CModule state elements are replicated to the new module table and the pointers are updated.
- If a module table is specifically crafted for a client but then a new one is pulled in from the internet, it could override the additional modules added to the client. Make it combine the two module tables, and only delete if its the server sending a table.