mirror of
https://github.com/quasar/Quasar.git
synced 2026-04-26 07:45:57 +03:00
[GH-ISSUE #181] New Keylogger chars like ^ or ` not working #77
Labels
No labels
bug
bug
cant-reproduce
discussion
duplicate
easy
enhancement
help wanted
improvement
invalid
need more info
pull-request
question
wont-add
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/Quasar#77
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @MaxXor on GitHub (May 23, 2015).
Original GitHub issue: https://github.com/quasar/Quasar/issues/181
To reproduce this issue run the client with keylogger enabled and press ^ (under Escape).
@DragonzMaster commented on GitHub (May 23, 2015):
~~++=_-)0(9*8&7^6%5$4#3@2!1~
~the above is what i wrote to test the keylogger and it seems to work for me :D
@ghost commented on GitHub (May 23, 2015):
This is working for me as well. What kind of keyboard do you have? Under my escape key is the tilde key (OemTilde), and my '^' key is (shift + 6)
@DragonzMaster, it looks like you are using the previous commits, could you try the new commits that were just added and try the same thing?
@ghost commented on GitHub (May 23, 2015):
@MaxXor, took a look here: http://clasfaculty.ucdenver.edu/tphillips/GermanKeyboardLayout.html
"The characters ² ³ { [ ] } \ @ € µ ~ are accessed by holding the Alt Gr key and tapping the other key.
The Alt key on the left will not access these additional characters.
The accent keys ^ ` ´ are dead keys (nothing happens until you type a second key).
Tap on an accent key once, let up, then tap on a vowel to produce accented characters. (ô á ù etc.)
Note that the semi-colon and colon are accessed by holding down the shift key (large arrow up)."
@ghost commented on GitHub (May 23, 2015):
Because these are dead keys, they won't be processed. Take a peek at the method at line 73 ('xClient.Core.Keylogger.WinApi.KeyboardNativeMethods')
@DragonzMaster commented on GitHub (May 23, 2015):
why should i use the last commit !!
the keylogger already works fine for me
but github almost doesn't show ' ~ when there are no spaces between them, instead it shows them like that
~~so every key i have pressed is logged correctly @d3agle
@ghost commented on GitHub (May 23, 2015):
@DragonzMaster , haha sorry!
@DragonzMaster commented on GitHub (May 23, 2015):
no problem bro
I hope you find a fix for @MaxXor problem
@MaxXor commented on GitHub (May 23, 2015):
lol yea I press ^ once and then again to show it, works fine without the keylogger. :(
@ghost commented on GitHub (May 23, 2015):
@MaxXor , When you say it works fine without the keylogger, do you mean that with the keylogger enabled and the client running, your ^ key doesn't function as it would without the keylogger enabled?
@MaxXor commented on GitHub (May 23, 2015):
Correct.
@ghost commented on GitHub (May 23, 2015):
Oh boy. I will look into this, that doesn't sound good
@ghost commented on GitHub (May 23, 2015):
@MaxXor , could you try something for me? I don't have a german keyboard to test this on, but I wonder if the dead key has a state that is being reset the first time you press it. I noticed that sometimes when starting the client with keylogger enabled, keys would be reset if they were already enabled. For example, if I had Numlock toggled off prior to starting the client, when I pressed Numlock to turn it on, it would turn it off as soon as i pressed and released it. I have a feeling this could be due to clearing the keyboard buffer in https://github.com/MaxXor/xRAT/blob/dev/Client/Core/Keylogger/WinApi/KeyboardNativeMethods.cs#L85.
Could you try using the key multiple times, to ensure the keyboard buffer is cleared by the time you next press your dead key? For example, Try accenting some characters a few times and see what it outputs.
@MaxXor commented on GitHub (May 23, 2015):
I did what you said, but it didn't work. I'll try removing this line and see what happens. :D
@ghost commented on GitHub (May 23, 2015):
Thanks! I just realized, someone recently raised this issue with the programmer who wrote this library, and he claims to have fixed it. I wonder if the problem is with our logic?
https://github.com/gmamaladze/globalmousekeyhook/issues/4
@MaxXor commented on GitHub (May 23, 2015):
Thanks, I've read it. Urutar also said it's not gone yet. :D Let's see if he can fix it!
@ghost commented on GitHub (May 24, 2015):
Sent a pull request with some fixes, along with a possible dead-key fix. #186, needs to be tested!
@ghost commented on GitHub (May 24, 2015):
Tested on Windows 8 VM with success!