starred/Quasar

Fork 0

mirror of https://github.com/quasar/Quasar.git synced 2026-04-26 07:45:57 +03:00

[GH-ISSUE #1140] Keylogger issue #833

New issue

Closed

opened 2026-02-27 15:52:02 +03:00 by kerem · 8 comments

kerem commented

2026-02-27 15:52:02 +03:00

Owner

Originally created by @thepersonalcomputer on GitHub (Mar 15, 2023).
Original GitHub issue: https://github.com/quasar/Quasar/issues/1140

Quasar version

1.4.1

Server installed .NET version

No response

Server operating system

Windows 11/Server 2022

Client installed .NET version

No response

Client operating system

Windows 11/Server 2022

Build configuration

Debug

Describe the bug

I'm running v 1.4.1 and for some reason some of the logs of the key logger will not decrypt and it just shows random symbols. Could somebody please help?

How to reproduce

Try key logger

Expected behavior

To be able to read logs.

Actual behavior

Cannot read them.

Additional context

No response

Originally created by @thepersonalcomputer on GitHub (Mar 15, 2023). Original GitHub issue: https://github.com/quasar/Quasar/issues/1140 ### Quasar version 1.4.1 ### Server installed .NET version _No response_ ### Server operating system Windows 11/Server 2022 ### Client installed .NET version _No response_ ### Client operating system Windows 11/Server 2022 ### Build configuration Debug ### Describe the bug I'm running v 1.4.1 and for some reason some of the logs of the key logger will not decrypt and it just shows random symbols. Could somebody please help? ### How to reproduce Try key logger ### Expected behavior To be able to read logs. ### Actual behavior Cannot read them. ### Additional context _No response_

kerem

2026-02-27 15:52:02 +03:00

closed this issue
added the
need more info
label

kerem commented

2026-02-27 15:52:02 +03:00

Author

Owner

@BurntDog commented on GitHub (Mar 15, 2023):

When this happens, Deleting the old log file prior to using keylogger may help.

@BurntDog commented on GitHub (Mar 15, 2023): When this happens, Deleting the old log file prior to using keylogger may help.

kerem commented

2026-02-27 15:52:02 +03:00

Author

Owner

@thepersonalcomputer commented on GitHub (Mar 15, 2023):

When this happens, Deleting the old log file prior to using keylogger may help.

On the client machine? On the host I assume that has to stay on all the time for the keylogger too?

@thepersonalcomputer commented on GitHub (Mar 15, 2023): > When this happens, Deleting the old log file prior to using keylogger may help. On the client machine? On the host I assume that has to stay on all the time for the keylogger too?

kerem commented

2026-02-27 15:52:02 +03:00

Author

Owner

@BurntDog commented on GitHub (Mar 15, 2023):

client machine, it will make a new one when keylogger is run/activated.

@BurntDog commented on GitHub (Mar 15, 2023): client machine, it will make a new one when keylogger is run/activated.

kerem commented

2026-02-27 15:52:02 +03:00

Author

Owner

@MaxXor commented on GitHub (Mar 15, 2023):

Did you update your clients from 1.4.0 to 1.4.1?

@MaxXor commented on GitHub (Mar 15, 2023): Did you update your clients from 1.4.0 to 1.4.1?

kerem commented

2026-02-27 15:52:02 +03:00

Author

Owner

@honkhewins commented on GitHub (Apr 28, 2023):

The solution is (if you selecetd appdata in quasar builder settings) is to remote access the machine, go to the user's appdata, then open the defaulty titled 'Logs' folder and delete all the logs. Then wait a minute and go back to quasar manager and click on the keylogging tool and make sure to select get logs and it should work.

@honkhewins commented on GitHub (Apr 28, 2023): The solution is (if you selecetd appdata in quasar builder settings) is to remote access the machine, go to the user's appdata, then open the defaulty titled 'Logs' folder and delete all the logs. Then wait a minute and go back to quasar manager and click on the keylogging tool and make sure to select get logs and it should work.

kerem commented

2026-02-27 15:52:02 +03:00

Author

Owner

@BurntDog commented on GitHub (May 6, 2023):

The solution is (if you selecetd appdata in quasar builder settings) is to remote access the machine, go to the user's appdata, then open the defaulty titled 'Logs' folder and delete all the logs. Then wait a minute and go back to quasar manager and click on the keylogging tool and make sure to select get logs and it should work.

What I said but in lesser words like over a month ago.

@BurntDog commented on GitHub (May 6, 2023): > The solution is (if you selecetd appdata in quasar builder settings) is to remote access the machine, go to the user's appdata, then open the defaulty titled 'Logs' folder and delete all the logs. Then wait a minute and go back to quasar manager and click on the keylogging tool and make sure to select get logs and it should work. What I said but in lesser words like over a month ago.

kerem commented

2026-02-27 15:52:02 +03:00

Author

Owner

@MaxXor commented on GitHub (May 6, 2023):

Do you think we should handle old keylogger logs differently, e.g. upgrading them (re-encrypt) to the new keys during a client update?

@MaxXor commented on GitHub (May 6, 2023): Do you think we should handle old keylogger logs differently, e.g. upgrading them (re-encrypt) to the new keys during a client update?

kerem commented

2026-02-27 15:52:02 +03:00

Author

Owner

@BurntDog commented on GitHub (May 6, 2023):

Do you think we should handle old keylogger logs differently, e.g. upgrading them (re-encrypt) to the new keys during a client update?

Only if you feel it's worth the time and would solve the occasional issue.
I realize you have enough to do.

@BurntDog commented on GitHub (May 6, 2023): > Do you think we should handle old keylogger logs differently, e.g. upgrading them (re-encrypt) to the new keys during a client update? Only if you feel it's worth the time and would solve the occasional issue. I realize you have enough to do.