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

New Campaign - Invalid Date Attack Breakdown #59

Closed
bzekanovic opened this issue May 23, 2022 · 4 comments
Closed

New Campaign - Invalid Date Attack Breakdown #59

bzekanovic opened this issue May 23, 2022 · 4 comments

Comments

@bzekanovic
Copy link

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
Copy link
Owner

c6fc commented May 23, 2022 via email

@bzekanovic
Copy link
Author

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
Copy link
Owner

c6fc commented May 23, 2022

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
Copy link
Author

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants