lawndoc / mediator Goto Github PK

New versions should automatically create a release and build the clients to publish with the release.

It's in the title. Why didn't I do this from the beginning?

The goal is to create a simple way for users to package up the clients with their dependencies and make them more portable. Especially for the reverse shell, this is very important for standalone usability.

Right now the reverse shell is limited and can't do things like tmux, vim, or even tab completion. I want to figure out a way to get an SSH-like session with colors and full TTY.

linuxTarget.py is still in pre-encryption implementation. The script needs to be updated to support end-to-end encryption like windowsTarget.py

Currently, the server knows a connection is from a permitted client based on a port-specific "knock" phrase sent upon connection. Adding an actual authentication method to ensure only permitted clients can connect would be more secure.

I want to functionally separate the initial connection that happens between the two clients including the key exchange up until the point where any reverse-shell specific data would be sent. The ability to bridge two client connections through a server and encrypt them end-to-end is independently useful and should be broken out into its own classes and potentially its own repository.

This will require a MAJOR refactor to the codebase. Off the top of my head, the following would be needed at a minimum:

At the connection level, the clients' roles will have to switch from the "operator-target" model to a single client type solely relying on being joined through connection key matching. This will require the key exchange to happen differently -- currently, the operator holds the private key and the target generates the asymmetric key. In reality, this can happen in the opposite direction. The first connection with a specific key can assume the role of the "operator" and the matching connection can assume the role of the "target" for the purposes of the key exchange. The clients' roles will have to be specified by the mediator server. Additionally, due to this change only a single port will be used.

edit: typo

After a plugin runs, the first half or so of the following prompt is cutting cut off. This appears to be an issue on the handler side because the target is sending the full prompt over the network. I think it might have something to do with the mutex that blocks output while a plugin is running.

Create a GHA workflow to build and publish a container image of the mediator server

When the e2eclient repository is finished, the package should be published to pypi. At that time, the e2eclient subrepository should be removed from this project and the package should be added as a requirement in requirements.txt

If possible through their licensing, include the needed packages from pycryptodome to remove the need to pip install it as a dependency for handler.py, linuxTarget.py, and windowsTarget.py

It would be really useful to have a custom command that allows you to push a file to the target host or pull a file from it. This should be reasonably simple to implement.