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

Possible wrong behaviour for O rule with -j/-k options #969

Closed
mhasbini opened this issue Jan 15, 2017 · 2 comments
Closed

Possible wrong behaviour for O rule with -j/-k options #969

mhasbini opened this issue Jan 15, 2017 · 2 comments
Assignees
Labels

Comments

@mhasbini
Copy link
Contributor

mhasbini commented Jan 15, 2017

1- When running O rule with -j/-k options with omit range equal to the provided plain it skip the plain.
2- When using the same rule from a file it works as expected.

first scenario

given file w.txt that contains the string abc.
and I run this command: hashcat --stdout -j 'O03' w.txt (or hashcat --stdout -k 'O03' w.txt).
then
expected output
`` ( empty )
actual
abc

second scenario

given file w.txt that contains the string abc.
and file rule.rule that contains the string O03.
and I run this command: hashcat --stdout -r rule.rule w.txt.
then
expected output
`` ( empty )
actual
as expected.

Hashcat version:

$ hashcat --version
v3.30-5-gdd57ef52

Is this an expected behaviour ?

@mhasbini mhasbini changed the title Wrong behaviour for O rule with -j/-k options Possible wrong behaviour for O rule with -j/-k options Jan 15, 2017
@jsteube jsteube self-assigned this Jan 23, 2017
@jsteube jsteube added the bug label Jan 23, 2017
@jsteube
Copy link
Member

jsteube commented Jan 23, 2017

No, it's a bug, not wanted behaviour. I can reproduce.

@jsteube
Copy link
Member

jsteube commented Jan 23, 2017

Fixed, thanks for reporting

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