Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

mouse click obfuscation #51

Open
adrelanos opened this issue Aug 16, 2023 · 1 comment
Open

mouse click obfuscation #51

adrelanos opened this issue Aug 16, 2023 · 1 comment

Comments

@adrelanos
Copy link
Contributor

When enabling debug mode -v I can see that mouse movements result in journal output. Not so for mouse clicks.

Are mouse clicks already obfuscated? Is this implemented or requires further work?

@skyzzuu
Copy link
Contributor

skyzzuu commented Aug 19, 2023

Yeah they have delay added to them. In the output, they'll be event type 1 (EV_KEY) and have a code of 272 (BTN_LEFT) for the left mouse button or 273 (BTN_RIGHT) for the right mouse buttn. I can see them in my output, they usually just get flooded by EV_REL events around them since the mouse will typically move at least a little bit when clicking one of the buttons. Then either 1 or 0 for value are button down and button released, but I can't remember which is which.

Towards the top of the large for loop in main_loop(), there are the following lines which will add delay to any events that aren't EV_SYN:

// syn events are not delayed
if (ev.type == EV_SYN) {
random_delay = lower_bound;
} else {

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

No branches or pull requests

2 participants