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

Default hash format used in attack - JtR Jumbo version #66

Open
shinnok opened this issue Jul 24, 2015 · 6 comments
Open

Default hash format used in attack - JtR Jumbo version #66

shinnok opened this issue Jul 24, 2015 · 6 comments
Assignees
Labels
Milestone

Comments

@shinnok
Copy link
Member

shinnok commented Jul 24, 2015

Via --show=types option. Can use the existing HashTypeChecker handler for this.

@shinnok shinnok added this to the 2.3 milestone Jul 24, 2015
@mathsoft-dev
Copy link
Collaborator

Information from Aleksey:
I think --show=types could do the job: the first format in the first
line with 1+ formats listed is the default one. But it is in jumbo
only.

@mathsoft-dev
Copy link
Collaborator

On a big file with 120k hashes, it takes 3 minutes 20 seconds to get the result from --show=types on my vm with only 2 cores . However, to get the default format from magnum idea #61 was instantaneous (I didn't time it but it was less than a second). Should we stick with #61 to show the default format faster to the user ?

@shinnok
Copy link
Member Author

shinnok commented Jul 31, 2015

I understand. In this case it's best to relay this information back on the list and then close this ticket.

@shinnok
Copy link
Member Author

shinnok commented Aug 13, 2015

@Math07 can you please write this piece of info back to the original thread on john-dev, Aleksey might think of this as useful. You can then close this ticket.

@mathsoft-dev
Copy link
Collaborator

I sent it to the list, I'll wait for answer.

@mathsoft-dev
Copy link
Collaborator

This still have the advantage that once you get the format list, you can deduce yourself the default format when user uncheck/check a row without reusing CPU. However, the result takes a lot longer to arrive on big hash file. Maybe if one day someone work on caching in QSettings the format for each row and use that if the last modified date of the file didn't change, otherwise recall --show=types, this could be cool for at least two reasons for big files.

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