[BUG] - Clean files into .yelaa directory

[jenaye]

currently when running an A-scan, in a and then a B scan, it takes the content of the A scan, and so does A+B, it would have to empty the osint files etc

[djnnvx]

If we change this variable into something that accepts a parameter (IP or URL), we can have a directory named .yelaa/scan-a and another one named .yelaa/scan-b with minimal change.

I am thinking of an optional parameter to YelaaPath (which should be turned into a function). If no argument is specified, we just return .yelaa, otherwise, we append / and the parameter specified.

Maybe it should also create the directory here if it does not exist, or it could be done in a separate function.

[darkweak]

The contents must be under the target URL (AFAIK sqlmap does that).
IMHO introduce a configurable .yelaa path would be good only if we let them to chose the whole path instead of a relative path to the .yelaa directory @bogdzn.

[djnnvx]

That's a good point, but then if we let them chose a specific path (I'm assuming this config is optionnal), what should be the default behaviour ? @darkweak

[darkweak]

We have to write data under {yelaa configured path}/{target url} (e.g. /home/user/dummy/my-scan/domain.com).
By default it should write in the .yelaa/domain.com.
With that there won't be the A+B scan issue unless the user tries to rescan the same domain.
I think about a dryrun option to remove the existing directory data if it already exists.

[djnnvx]

Ok, so to sum it up:

• add a dryrun CLI option to test and remove existing data if it exists
• add a path option to configure the out-directory of the scans
• scan results should be stored in a sub-directory inside the pre-configured directory

Is it correct ? I already got started on it, I don't want to miss anything

[darkweak]

I agree 👍.

[djnnvx]

Fixed in #60 ! :)~