[GH-ISSUE #119] multible (repeated) key in keylog and very long line #56

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

Originally created by @DragonzMaster on GitHub (May 10, 2015).
Original GitHub issue: https://github.com/quasar/Quasar/issues/119

when you play as an example and you open the keylog
you see something like that
[Call of Duty® Ghosts]
wwwssssssssssssssssssssssss3wwwwwwwwwwwwwwwssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssrwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwww

you can see that the letter is repeted many times which is someway annoying
so it is possible to make changes to prevent that


and another thing the line is too too long :/
and it is very annoying to scroll horizontally for long time
so can we limit the line char number (70 characters for example)
so it can be more comfortable
*note : i copied a very small sample of the keylog just to clarify the problem and it was really too long

Originally created by @DragonzMaster on GitHub (May 10, 2015). Original GitHub issue: https://github.com/quasar/Quasar/issues/119 when you play as an example and you open the keylog you see something like that [Call of Duty® Ghosts] wwwssssssssssssssssssssssss3wwwwwwwwwwwwwwwssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssrwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwww you can see that the letter is repeted many times which is someway annoying so it is possible to make changes to prevent that --- and another thing the line is too too long :/ and it is very annoying to scroll horizontally for long time so can we limit the line char number (70 characters for example) so it can be more comfortable *note : i copied a very small sample of the keylog just to clarify the problem and it was really too long
kerem 2026-02-27 15:48:31 +03:00
Author
Owner

@yankejustin commented on GitHub (May 11, 2015):

What do you suggest we do about repetitive keystrokes?

<!-- gh-comment-id:101058862 --> @yankejustin commented on GitHub (May 11, 2015): What do you suggest we do about repetitive keystrokes?
Author
Owner

@ghost commented on GitHub (May 11, 2015):

This reference might contain a solution: http://stackoverflow.com/a/9356006

<!-- gh-comment-id:101060044 --> @ghost commented on GitHub (May 11, 2015): This reference might contain a solution: http://stackoverflow.com/a/9356006
Author
Owner

@DragonzMaster commented on GitHub (May 11, 2015):

like if the key is pressed it won't be logged more than once unless if i put up my finger and press it again
is it possible ? @yankejustin

<!-- gh-comment-id:101060068 --> @DragonzMaster commented on GitHub (May 11, 2015): like if the key is pressed it won't be logged more than once unless if i put up my finger and press it again is it possible ? @yankejustin
Author
Owner

@ghost commented on GitHub (May 11, 2015):

To be fair I don't see this as a problem, but I think I know a way to fix it

<!-- gh-comment-id:101063864 --> @ghost commented on GitHub (May 11, 2015): To be fair I don't see this as a problem, but I think I know a way to fix it
Author
Owner

@yankejustin commented on GitHub (May 11, 2015):

Yes, it is absolutely possible. However, without this behavior someone that does this intentionally when typing something can cause loss of accuracy.

<!-- gh-comment-id:101074232 --> @yankejustin commented on GitHub (May 11, 2015): Yes, it is absolutely possible. However, without this behavior someone that does this intentionally when typing something can cause loss of accuracy.
Author
Owner

@DragonzMaster commented on GitHub (May 11, 2015):

may be (it is your opinion) but it is logs unnecessary keys which make the log looks bad and what can i benefit from a log contains hundreds of repeated "s" and "w" and similar keys used
and it increase Line's Length and log's size @d3agle

<!-- gh-comment-id:101074294 --> @DragonzMaster commented on GitHub (May 11, 2015): may be (it is your opinion) but it is logs unnecessary keys which make the log looks bad and what can i benefit from a log contains hundreds of repeated "s" and "w" and similar keys used and it increase Line's Length and log's size @d3agle
Author
Owner

@yankejustin commented on GitHub (May 11, 2015):

Well, I am not speaking of my opinion, I am speaking factually. Purposely ignoring subsequent keystrokes due to their proximity is an intentional loss of data (or the accuracy of data).

<!-- gh-comment-id:101074508 --> @yankejustin commented on GitHub (May 11, 2015): Well, I am not speaking of my opinion, I am speaking factually. Purposely ignoring subsequent keystrokes due to their proximity is an intentional loss of data (or the accuracy of data).
Author
Owner

@DragonzMaster commented on GitHub (May 11, 2015):

so can we make it optional ? @yankejustin
i was talking to @d3agle in my previous comment
Edit : I respect both of your views so do what you see it is suitable

<!-- gh-comment-id:101074681 --> @DragonzMaster commented on GitHub (May 11, 2015): so can we make it optional ? @yankejustin i was talking to @d3agle in my previous comment Edit : I respect both of your views so do what you see it is suitable
Author
Owner

@yankejustin commented on GitHub (May 12, 2015):

Certainly an optional thing because there are many cases to where it is necessary to show them.
One way I can think of is to generate a collapsible table (basic html).

<!-- gh-comment-id:101077690 --> @yankejustin commented on GitHub (May 12, 2015): Certainly an optional thing because there are many cases to where it is necessary to show them. One way I can think of is to generate a collapsible table (basic html).
Author
Owner

@DragonzMaster commented on GitHub (May 12, 2015):

ok
now what about Line Char number limitation (the second part of issue) to prevent the line from being too long ?

<!-- gh-comment-id:101083485 --> @DragonzMaster commented on GitHub (May 12, 2015): ok now what about Line Char number limitation (the second part of issue) to prevent the line from being too long ?
Author
Owner

@yankejustin commented on GitHub (May 12, 2015):

Personally I think that the keylogger should be making a folder for each day anyways... Then place a limited amount of data in each file to divide them up.

<!-- gh-comment-id:101084260 --> @yankejustin commented on GitHub (May 12, 2015): Personally I think that the keylogger should be making a folder for each day anyways... Then place a limited amount of data in each file to divide them up.
Author
Owner

@bitterypaul commented on GitHub (May 12, 2015):

if same key is repeated more than 5 times, then we can make keylogger to log it as 5[w]

<!-- gh-comment-id:101121618 --> @bitterypaul commented on GitHub (May 12, 2015): if same key is repeated more than 5 times, then we can make keylogger to log it as 5[w]
Author
Owner

@m6m4m2 commented on GitHub (May 12, 2015):

Nice work you guys I have an idea here's a picture to explain it

http://mizr.org/p/f/repository/z/01.gif

if you think its useful I'll release the source if not .. will then I'll think of another solution

<!-- gh-comment-id:101124142 --> @m6m4m2 commented on GitHub (May 12, 2015): Nice work you guys I have an idea here's a picture to explain it http://mizr.org/p/f/repository/z/01.gif if you think its useful I'll release the source if not .. will then I'll think of another solution
Author
Owner

@bitterypaul commented on GitHub (May 12, 2015):

correct me if i am wrong. since quicklz is used, the log will be compressed. so the log will shrink in its size during transmission.

<!-- gh-comment-id:101124151 --> @bitterypaul commented on GitHub (May 12, 2015): correct me if i am wrong. since quicklz is used, the log will be compressed. so the log will shrink in its size during transmission.
Author
Owner

@yankejustin commented on GitHub (May 12, 2015):

@xmizrx That would be a useful addition to the keylogger. :)
I was actually thinking the same thing when I looked back at the logs and realized how inaccurate I am with a keyboard! x)

<!-- gh-comment-id:101129417 --> @yankejustin commented on GitHub (May 12, 2015): @xmizrx That would be a useful addition to the keylogger. :) I was actually thinking the same thing when I looked back at the logs and realized how inaccurate I am with a keyboard! x)
Author
Owner

@m6m4m2 commented on GitHub (May 12, 2015):

@yankejustin Thanks here's the source although it still has some bugs but simple to fix

you need

3* textboxs
2* buttons
1* timer

The source

using System;
using System.Collections.Generic;
using System.ComponentModel;
using System.Data;
using System.Drawing;
using System.Text;
using System.Windows.Forms;

namespace xServer.Forms
{
public partial class FrmRePlay : Form
{
public FrmRePlay()
{
InitializeComponent();
}
private int i;
private string strMessage;

    private void start_Click(object sender, EventArgs e)
    {
        string str;
        string str1;
        str1 = "";
        str = in1.Text;
        while (((str.IndexOf("[Back]") + 1)
                    != 0))
        {
            str1 = str.Substring((str.IndexOf("[Back]") + 6));
            str = fun(str.Substring(0, str.IndexOf("[Back]")));
            str = (str + str1);
        }
        in2.Text = str;
        //  will give the output
        i = 0;
        TextReplay.Text = "";
        timer1.Enabled = true;
        strMessage = in2.Text;
    }

    private void stop_Click(object sender, EventArgs e)
    {
        timer1.Stop();
    }
    public string fun(string str)
    {
        return str.Remove((str.Length - 1), 1);
    }

    private void timer1_Tick(object sender, EventArgs e)
    {
        i++;
        TextReplay.Text = (TextReplay.Text + strMessage.Substring((i - 1), 1));
        if ((i == strMessage.Length))
        {
            timer1.Enabled = false;
        }
        if (strMessage.Contains("[Enter]"))
        {
            strMessage = strMessage.Replace("[Enter]", "\r\n");
        }
    }

    private void FrmRePlay_Load(object sender, EventArgs e)
    {
        in1.Text = Clipboard.GetText();
        string str;
        string str1;
        str1 = "";
        str = in1.Text;
        while (((str.IndexOf("[Back]") + 1)
                    != 0))
        {
            str1 = str.Substring((str.IndexOf("[Back]") + 6));
            str = fun(str.Substring(0, str.IndexOf("[Back]")));
            str = (str + str1);
        }
        in2.Text = str;
        //  will give the output
        i = 0;
        TextReplay.Text = "";
        timer1.Enabled = true;
        strMessage = in2.Text;
    }
}

}

<!-- gh-comment-id:101134249 --> @m6m4m2 commented on GitHub (May 12, 2015): @yankejustin Thanks here's the source although it still has some bugs but simple to fix # you need 3\* textboxs 2\* buttons 1\* timer # The source using System; using System.Collections.Generic; using System.ComponentModel; using System.Data; using System.Drawing; using System.Text; using System.Windows.Forms; namespace xServer.Forms { public partial class FrmRePlay : Form { public FrmRePlay() { InitializeComponent(); } private int i; private string strMessage; ``` private void start_Click(object sender, EventArgs e) { string str; string str1; str1 = ""; str = in1.Text; while (((str.IndexOf("[Back]") + 1) != 0)) { str1 = str.Substring((str.IndexOf("[Back]") + 6)); str = fun(str.Substring(0, str.IndexOf("[Back]"))); str = (str + str1); } in2.Text = str; // will give the output i = 0; TextReplay.Text = ""; timer1.Enabled = true; strMessage = in2.Text; } private void stop_Click(object sender, EventArgs e) { timer1.Stop(); } public string fun(string str) { return str.Remove((str.Length - 1), 1); } private void timer1_Tick(object sender, EventArgs e) { i++; TextReplay.Text = (TextReplay.Text + strMessage.Substring((i - 1), 1)); if ((i == strMessage.Length)) { timer1.Enabled = false; } if (strMessage.Contains("[Enter]")) { strMessage = strMessage.Replace("[Enter]", "\r\n"); } } private void FrmRePlay_Load(object sender, EventArgs e) { in1.Text = Clipboard.GetText(); string str; string str1; str1 = ""; str = in1.Text; while (((str.IndexOf("[Back]") + 1) != 0)) { str1 = str.Substring((str.IndexOf("[Back]") + 6)); str = fun(str.Substring(0, str.IndexOf("[Back]"))); str = (str + str1); } in2.Text = str; // will give the output i = 0; TextReplay.Text = ""; timer1.Enabled = true; strMessage = in2.Text; } } ``` }
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#56
No description provided.