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

Keylogger update#158

Merged
MaxXor merged 6 commits intoquasar:devfrom
yankejustin:Keylogger
May 21, 2015
Merged

Keylogger update#158
MaxXor merged 6 commits intoquasar:devfrom
yankejustin:Keylogger

Conversation

@yankejustin
Copy link
Copy Markdown
Contributor

Notable Changes

I implemented gmamaladze's logic into the Keylogger. I feel it would be a good idea to merge into dev because it would be a more convenient spot for others to collaborate on the current progress.

Status

After testing, output functions as desired when wired to a Form-based process. Perhaps @d3agle can help with getting this message pump implemented correctly, as I am not as knowledgeable when it comes to things regarding that subject (yet). Once the message pump is implemented as it should be, the output logic plugs in nicely to the way I implemented it into the Keylogger and the data will flow like rivers. ;)

Notes

I left a few prior commits for possible future usage and documentation. Some of the old commits have pieces of code that can be used to implement new features once this version is up to speed.

Merge with dev branch
Modified a few things... Saving current spot to for major content
additions.
Implemented gmamaladze's logic into the Keylogger. Still needs work on
the way it outputs. See additional notes in
#149
Updated README to reflect the usage of George Mamaladze's work.
@ghost
Copy link
Copy Markdown

ghost commented May 21, 2015

I'm working on finding a clean solution implement Application.Run() on the logger thread, but its seemingly a challenge. For now, I think the main focus should be getting the key logger working properly as far as key combinations/logging keys, etc goes. Something that might deem useful could include the KeyloggerKeys enumeration you wrote to get specific values for certain keys since we are working with the same values in the Keys enumerations.

@yankejustin
Copy link
Copy Markdown
Contributor Author

I have been testing the output of the code itself in a windows forms program. The output is correct and works as we hoped :)
I just want to get the output to work so we have something to work with. At this point, I just want to be able to know where to look if I want to reflect back on commits and point to one that works as intended (not perfectly, but works)...
Once we get this working as desired, then we should start with these cool feature additions (such as using the old KeyloggerKeys enumeration to get more specific values). 💯

@yankejustin
Copy link
Copy Markdown
Contributor Author

@d3agle Don't worry if it is dirty or hacky. I just need anything that correctly hooks up with the Keylogger. I can always go back and clean up. 🐼

@ghost
Copy link
Copy Markdown

ghost commented May 21, 2015

@yankejustin, Sounds good! I've got key combinations working very nicely at the moment. I will send a pull request shortly after I've thought over other solutions (Not that it is too hacky ;D)

MaxXor added a commit that referenced this pull request May 21, 2015
@MaxXor MaxXor merged commit 28f3fe1 into quasar:dev May 21, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants