[GH-ISSUE #14] Remote Shell #6

Closed
opened 2026-02-27 15:48:14 +03:00 by kerem · 3 comments
Owner

Originally created by @madified on GitHub (Jan 13, 2015).
Original GitHub issue: https://github.com/quasar/Quasar/issues/14

It is indeed a great effort. There's just a little bug. On server end remote shell is displaying 2nd last response instead of latest one.

Originally created by @madified on GitHub (Jan 13, 2015). Original GitHub issue: https://github.com/quasar/Quasar/issues/14 It is indeed a great effort. There's just a little bug. On server end remote shell is displaying 2nd last response instead of latest one.
kerem 2026-02-27 15:48:14 +03:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@MaxXor commented on GitHub (Jan 13, 2015):

Can you tell me the steps to reproduce this issue? I don't have this on my test machine.

<!-- gh-comment-id:69798558 --> @MaxXor commented on GitHub (Jan 13, 2015): Can you tell me the steps to reproduce this issue? I don't have this on my test machine.
Author
Owner

@madified commented on GitHub (Jan 15, 2015):

No idea how to fix it.. I was working on keylogger.. Finally built a stable and virus clean keylogger for xRAT but after you 3rd last commit xRAT client is unstable ( Windows 8.1 ). (Right after client execution process stops. Please Check.)

Looking forward to collaborate for keylogger in xRAT.

<!-- gh-comment-id:70062300 --> @madified commented on GitHub (Jan 15, 2015): No idea how to fix it.. I was working on keylogger.. Finally built a stable and virus clean keylogger for xRAT but after you 3rd last commit xRAT client is unstable ( Windows 8.1 ). (Right after client execution process stops. Please Check.) Looking forward to collaborate for keylogger in xRAT.
Author
Owner

@MaxXor commented on GitHub (Jan 15, 2015):

Can you please download the latest source again and build it. Check if the problem still occurs and try to step through the source with the debugger to find out where the problem occurs.

The last 3 commits have nothing to do with the client stability in general, only when you call these functions.

//edit: Could you also please create a new issue with these details. Thanks!

<!-- gh-comment-id:70063646 --> @MaxXor commented on GitHub (Jan 15, 2015): Can you please download the latest source again and build it. Check if the problem still occurs and try to step through the source with the debugger to find out where the problem occurs. The last 3 commits have nothing to do with the client stability in general, only when you call these functions. //edit: Could you also please create a new issue with these details. Thanks!
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/Quasar#6
No description provided.