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

[Bug]: Piping candidates to Hashcat not working on Windows #1705

Open
s3inlc opened this Issue Sep 27, 2018 · 2 comments

Comments

Projects
None yet
3 participants
@s3inlc

s3inlc commented Sep 27, 2018

When piping the password candidates to the newest Hashcat (e.g. with PRINCE), it does not process the input but stops immediately just after starting. Example:

prince.exe example.dict | hashcat64.exe -m 400 -a 0 hashlist.txt

With older Hashcat versions (e.g. 4.1.0) this was working. And it only does not work on Windows, on Linux it is still working fine.

@philsmd

This comment has been minimized.

Show comment
Hide comment
@philsmd

philsmd Oct 16, 2018

Member

I did try to reproduce this on windows 10 with both hashcat 4.2.0 and 4.2.1 and both worked correctly.

I've tested it with

echo hashcat|hashcat64.exe -m 400 hashlist.txt

and

type dict.txt | hashcat64.exe -m 400 hashlist.txt

and

pp64.exe dict2.txt | hashcat64.exe -m 400 hashlist.txt

all of these commands succeeded and cracked the hashes as expected.

I'm not sure how to reproduce this. Did you test with a different version (non release versions)?
if not, can you please test again with a different windows 10 system (maybe it's a problem with your driver/setup)?

Member

philsmd commented Oct 16, 2018

I did try to reproduce this on windows 10 with both hashcat 4.2.0 and 4.2.1 and both worked correctly.

I've tested it with

echo hashcat|hashcat64.exe -m 400 hashlist.txt

and

type dict.txt | hashcat64.exe -m 400 hashlist.txt

and

pp64.exe dict2.txt | hashcat64.exe -m 400 hashlist.txt

all of these commands succeeded and cracked the hashes as expected.

I'm not sure how to reproduce this. Did you test with a different version (non release versions)?
if not, can you please test again with a different windows 10 system (maybe it's a problem with your driver/setup)?

@jsteube

This comment has been minimized.

Show comment
Hide comment
@jsteube

jsteube Oct 17, 2018

Member

I can reproduce this with the following command:

type example.dict | hashcat64.exe -m 400 example400.hash

But it requires the latest github master version (or binary beta from hashcat.net/beta). Older versions 4.1.0, 4.2.0 and 4.2.1 seem not affected.

Member

jsteube commented Oct 17, 2018

I can reproduce this with the following command:

type example.dict | hashcat64.exe -m 400 example400.hash

But it requires the latest github master version (or binary beta from hashcat.net/beta). Older versions 4.1.0, 4.2.0 and 4.2.1 seem not affected.

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