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

improve UX for file targets that do not write cracks to potfile #2554

Closed
roycewilliams opened this issue Sep 25, 2020 · 2 comments · Fixed by #3182
Closed

improve UX for file targets that do not write cracks to potfile #2554

roycewilliams opened this issue Sep 25, 2020 · 2 comments · Fixed by #3182

Comments

@roycewilliams
Copy link
Member

Reference thread: https://hashcat.net/forum/thread-9490-post-50261.html#pid50261

A couple of suggestions:

  • Consider restoring writing to potfile specifically for the formats that are filename-based

  • If that's not attractive, consider generating a warning-level message to the user saying something like "WARNING: This format does not write cracks to the potfile - use -o" or something like that

@roycewilliams
Copy link
Member Author

Just curious - what is the reason for not writing to the potfile? The previous behavior was simple and convenient.

@Chick3nman
Copy link
Contributor

I believe it's to do with colliding entries in the potfile causing you to have to disable the potfile anyway if the entry is not a match. We throw other warnings like the warning for --keep-guessing about that dangers of duplicate entries in the potfile.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants