search

c6fc / npk

A mostly-serverless distributed hash cracking platform
508 stars 59 forks source link

New Campaign - Invalid Date Attack Breakdown #59

Closed bzekanovic closed 2 years ago

bzekanovic commented 2 years ago

When selecting certain wordlists uses are getting below attack breakdown. Do I need to re-upload wordlists in order for NPK to process these in back end?

image

c6fc commented 2 years ago

Do you have an instance selected?

On Mon, May 23, 2022 at 9:01 AM bzekanovic @.***> wrote:

When selecting certain wordlists uses are getting below attack breakdown. Do I need to re-upload wordlists in order for NPK to process these in back end?

[image: image] https://user-images.githubusercontent.com/16389468/169848719-ca7bf520-a8ec-4add-a0ba-d8795ca61af0.png

— Reply to this email directly, view it on GitHub https://github.com/c6fc/npk/issues/59, or unsubscribe https://github.com/notifications/unsubscribe-auth/AABDAN6PMKMTHHQZYGM2KYLVLOMUFANCNFSM5WWE4MQA . You are receiving this because you are subscribed to this thread.Message ID: @.***>

-- Brad Woodward AWS PSA+SCS, OSCP, OSCE, MCITP, MCSA, CISSP-ISSAP, CRISC, CPSA, CRT

@.*** @bradwoodward_io

bzekanovic commented 2 years ago

Yes, I have the instance selected. Could this be related to that issue where wordlist upload process was timing out we were looking at couple of weeks ago and you had me just upload the wordlist directly into s3?

c6fc commented 2 years ago

You shouldn't upload them directly to the wordlist/ prefix in S3 - the metadata won't get populated. If you uploaded it directly to the wordlist/ prefix through the console, then that's definitely the reason you won't see date details, and you'll probably get campaign execution errors or exceed the disk space of the nodes if you try to use them.

You can manually upload it to the to_process/wordlist prefix, which is technically the same thing that happens if you use the dictionary management view in the console. If you were using an oversized file before commit 3827504 (April 24th), then you could try again and see if the new handling works for your large file.

Give that a shot if this file was uploaded before April 24th, or update and reupload if you're using a version of NPK from before that date. Keep in might that really big files take a long time to compress (something like an hour per 20GiB uncompressed on these instances), so stay patient if you're uploading a really big wordlist.

bzekanovic commented 2 years ago

Looks like I just had to update NPK with your latest commit so it can process larger wordlists. thx