Problem with STDIN
#1
I'm writing a program that launches hashcat as a subprocess that redirects STDIN and STDOUT to files, but now upon launch I always get:

stdin: Bad file descriptor

Here's the complete output:

Code:
oclHashcat-plus v0.15 by atom starting...

Hashes: 1 total, 1 unique salts, 1 unique digests
Bitmaps: 8 bits, 256 entries, 0x000000ff mask, 1024 bytes
Workload: 2048 loops, 8 accel
Watchdog: Temperature abort trigger disabled
Watchdog: Temperature retain trigger disabled
Device #1: Tahiti, 2764MB, 900Mhz, 32MCU
Device #2: Tahiti, 2764MB, 900Mhz, 32MCU
Device #3: Tahiti, 2764MB, 900Mhz, 32MCU
Device #1: Kernel ./kernels/4098/m2500.Tahiti_1268.1_1268.1 (VM).kernel not found in cache! Building may take a while...
Device #1: Kernel ./kernels/4098/m2500.Tahiti_1268.1_1268.1 (VM).kernel (1350264 bytes)
Device #2: Kernel ./kernels/4098/m2500.Tahiti_1268.1_1268.1 (VM).kernel (1350264 bytes)
Device #3: Kernel ./kernels/4098/m2500.Tahiti_1268.1_1268.1 (VM).kernel (1350264 bytes)

stdin: Bad file descriptor

Is there any workaround for this? I don't know exactly what hashcat is trying to do with STDIN so I can't tell what I'm doing wrong on my side.
#2
whats the command line you are running?
#3
hc -m 0 -a 3 -i -1 0123456789 hashes ?1?1?1?1?1?1?1?1?1?1

It works fine when I type it into a command line directly, but not when launched from the wrapper app.

To be clear, the wrapper app does not create a handle to STDIN - I think that's the problem. Is there any way to stop hashcat from looking for a STDIN handle? I tried --quiet but that didn't help.
#4
What you mean by not looking for a STDIN handle? If we want to read from it, it must be opened.