Window keylogger

[deadex-ng]

@SANTHOSH17-DOT - I had issues with the previous keylogger here. I'm on windows and the file can't run, windows automatically deletes the main.py. From the readme, I think it works only on Kali

I created another keylogger for windows. Functionalities:

• It saves the log file.

Here is what the log file looks like:

Date - 2023-01-03 12:49:19.980322 | Timestamp - 1672742960
Window - Groove Music
Keys - 
j | 36 | 1672742938
l | 38 | 1672742938
k | 37 | 1672742938
f | 33 | 1672742939
j | 36 | 1672742939
l | 38 | 1672742939
j, l, k, f, j, l

The columns are key name, scan code, and time and the last line is a combination of all the key names.

I will add more functionality to key kelogger after this PR

[deadex-ng]

@SANTHOSH17-DOT I have added a workflow to check Python code format using black.

[SANTHOSH17-DOT]

Looks great @deadex-ng. Could you create two subdirectories within keyloggers - one for windows and another for kali? Let the kali version of the key logger be there. Also, Please squash all your commits into fewer commits

[deadex-ng]

@SANTHOSH17-DOT I'm not able to add the keylogger for Kali. Every time I open the project, the main.py is automatically deleted.

[SANTHOSH17-DOT]

Oh. I'll take a local copy of it and push it later. Just squash the commits. Please include screenshots/ a screen recording in the readme of this directory. I am giving SWOC - Medium badge to this PR. I hope you are fine with it

[deadex-ng]

@SANTHOSH17-DOT I have messed up when I was squashing the commits.

[SANTHOSH17-DOT]

No worries. Is your work safe? Create a new branch from the main branch of your fork and copy your work there. Try this @deadex-ng

[deadex-ng]

No worries. Is your work safe? Create a new branch from the main branch of your fork and copy your work there. Try this @deadex-ng

@SANTHOSH17-DOT My work is safe. Let me do what you've said.