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

Non-printable or control chars in the Password field #46

Open
shinnok opened this issue Jun 26, 2015 · 7 comments
Open

Non-printable or control chars in the Password field #46

shinnok opened this issue Jun 26, 2015 · 7 comments
Assignees
Labels
Milestone

Comments

@shinnok
Copy link
Member

shinnok commented Jun 26, 2015

We need to indicate non-printable or control chars too in the Password field. Maybe encoding to something like UTF would work for passwords containing such chars.

@shinnok shinnok added this to the 2.1 milestone Jun 30, 2015
@shinnok shinnok modified the milestones: 2.2, 2.1 Jul 24, 2015
@mathsoft-dev
Copy link
Collaborator

I don't really understand this issue.
Use case :

  1. We get a control char from John --show. 1) Which encoding is john --show, is it ascii or utf-8,utf-16 ? 2) Are we talking about the ASCII control characters only 0-31 (http://www.ascii-code.com/) ?
  2. We have lines :
    QByteArray output = m_johnShow.readAllStandardOutput();
    QTextStream outputStream(output);
    We can set codec to the QTextStream there.

@mathsoft-dev
Copy link
Collaborator

Also, please explain me your theory on why using UTF could show unprintable characters in the table view ?

@mathsoft-dev
Copy link
Collaborator

Also, please explain me your theory on why using UTF could show unprintable characters in the table view ?

My current john.pot contains non-ascii character such as Д from the CMIYC contest and when I call outputStream.codec()->name() , without changing anything in current/master johnny code, I get "UTF-8" and this character is printed out correctly in the table view. So, maybe the Qtextstream already always choose utf or auto-detect it based on john --show output.

@shinnok
Copy link
Member Author

shinnok commented Aug 18, 2015

Non-printable is different than non-ascii chars. Ascii includes non-printable chars like carriage return or backspace. UTF char space is not a problem given that we use Qt.

http://www.juniper.net/documentation/en_US/idp5.1/topics/reference/general/intrusion-detection-prevention-custom-attack-object-extended-ascii.html

@shinnok
Copy link
Member Author

shinnok commented Aug 18, 2015

UTF support in JtR is only a recent thing and jumbo only afaik. I guess we have to work with what John outputs. The first thing to try is to see how JtR prints ascii control chars or ask on the list. I think Frank asked for this in a thread, track it down if you can and reply there.

@mathsoft-dev
Copy link
Collaborator

Here is magnum answer :
On 2015-08-18 14:23, Mathieu Laprise wrote:
Shinnok want to indicate non-printable or control chars in Johnny's
Password field for core and jumbo. We're not really experimented with
encoding. How does JtR prints ascii control chars in john --show ?

It just prints them. A tab is printed as a tab, an \x07 might ring a bell. It's normally not an issue since no-one has them in real passwords.

@shinnok shinnok modified the milestones: 2.3, 2.2 Aug 20, 2015
@shinnok
Copy link
Member Author

shinnok commented Aug 20, 2015

Based on Frank's and Magnum's feedback I'm moving this task to a later milestone.

The way this should be handled, is to provide means for showing all passwords in hex encoding, via a checkbox or right click context menu.

@shinnok shinnok modified the milestones: 2.3, 3.0 Apr 7, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants