Misconfigured file ClassifierRule

[rzdhop]

Hi,
I've got an issue, the exe work perfectly but here is the printing :

I've tried to recompile the exe myself just in case, but still.
I have to say that the scan works, just there are those errors popping and over flooding my screen.

[l0ss]

Can you please provide the full set of arguments that you're using to run it? I've just tested the 1.0.112 release with Snaffler.exe -s -i C:\ and it seems to be working fine with none of the errors you're showing above.

[rzdhop]

Yes ofc, (i'm using the latest release too)
snaffler.exe -y -o 'result.tsv' -s -j 150 -d 'domain.local' -b 2 -c 'domain.local'
I'm trying to scan all shares accross an entire domain, I don't have the issue without the -b parameter (but i need it, or else too many things are returned)

[l0ss]

yeah ok this is a bug in how the -b functionality works, i'll try to figure it out when i have some time - in the meantime i suggest running without -b and just use good old fashioned grep to filter out the lower triage levels.

[Zamanry]

Just ran into this same issue. The command I was using was:

& snaffler.exe -s -o "Snaffler.txt" -d domain.tld -c dc.domain.tld -b 3

I would offer an exact version, but cannot find a version using the help menu (binary from two years ago). Tried again with 1.0.140 to no avail. (I have read the above chain, but wanted to reinforce the bug's importance.)

[l0ss]

I'm trying to reproduce this - does this occur immediately when you run Snaffler or does it happen when it hits a certain type of file?

[Zamanry]

From my memory, I believe the error appeared when it hit a certain file. I know my teams run into this a lot. We run this against entire domains. So I don’t have the info of which share/host was the issue.