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

Add loot directory integrity check #60

Closed
menzow opened this issue May 14, 2017 · 3 comments
Closed

Add loot directory integrity check #60

menzow opened this issue May 14, 2017 · 3 comments

Comments

@menzow
Copy link
Contributor

menzow commented May 14, 2017

Hey,

In a recent update the loot directory initialisation has been removed changed?, this causes fresh installs to break because most of the tools don't create intermediate directories.

I suggest the loot dirs integrity is checked when sniper is initialised and that any missing loot directories are created before continuing.

Edit:
Apparently it has not been removed, but I do think it was changed. Can't find the exact commit.

@1N3
Copy link
Owner

1N3 commented May 14, 2017

I added an init function at the top of the script to init the loot directory every time sniper runs. Should be fixed now in 2.4c.

@menzow
Copy link
Contributor Author

menzow commented May 15, 2017

Great! Encountered the issue while doing a big polish on the docker image.

Biggest changes listed here: menzow/sn1per-docker@5508afc

Most important change is that there's a VOLUME which persists the scan reports to your host operating system, and another VOLUME that allows you to add your own wordlists etc. Oh and I added xvfb so cutycapt actually take screenshots.

Right now still running some tests, expect to push the release to hub.docker.com somewhere this week.

@1N3
Copy link
Owner

1N3 commented May 16, 2017

Cool man, I'll check it out! 👍

@1N3 1N3 closed this as completed May 16, 2017
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