Skip to content
This repository has been archived by the owner on Mar 17, 2024. It is now read-only.

Adding feature to stop/start keylogger after running the client on remote machine #199

Open
DragonzMaster opened this issue May 25, 2015 · 6 comments

Comments

@DragonzMaster
Copy link
Contributor

when we open the keylogger form can we send a request to the client to get keylogger statue (On/Off)
if it is turned off a button (will be added to keylogger form ) will be enabled and when we press it the keylogger starts its work and vice-versa

@ghost
Copy link

ghost commented May 25, 2015

There could be a dynamic client settings file that is added that the command handler could read/write to and from

@MaxXor
Copy link
Contributor

MaxXor commented May 25, 2015

No, we will just set a lock file in the Logs folder when the Keylogger should be disabled.
We can easily remove/add (on/off) this file.

@DragonzMaster
Copy link
Contributor Author

or it could be a registry value
that depends on file's GUID for example

@yankejustin
Copy link
Contributor

@MaxXor Like an XML settings file used by the builder form?

@yankejustin
Copy link
Contributor

https://github.com/MaxXor/xRAT/blob/eaf89ef97b953d88e5039f221ae866c1b63e1072/Client/Program.cs#L143
We got the handle to the logger, so we should be able to very easily just store it internally and tell it to Dispose when we are done with it!

@yankejustin
Copy link
Contributor

After disposing it, we can just poke with this value if we wish to enable or disable on startup https://github.com/MaxXor/xRAT/blob/eaf89ef97b953d88e5039f221ae866c1b63e1072/Client/Program.cs#L138

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants