Skip to content
This repository has been archived by the owner on May 14, 2022. It is now read-only.

Feature Request: Local Extraction Directory Name #113

Open
GoogleCodeExporter opened this issue May 8, 2015 · 0 comments
Open

Feature Request: Local Extraction Directory Name #113

GoogleCodeExporter opened this issue May 8, 2015 · 0 comments

Comments

@GoogleCodeExporter
Copy link

Currently when the system pulls down compressed files for extraction, and when 
it sets up mount points the extraction directory and mount point name used 
appears to be based upon a incremented numeric value. In cases where the mount 
or the scan fails to clean up after itself (there maybe other cases), the 
extraction directory or mount point may not be removed cleanly. Additionally, 
when multiple scans are running concurrently its not always easy to distinguish 
which extraction directory or mount point is related to which scan.


Is it possible to change the way this value is generated to match the 
$scan_name-$scan_target-$value, or some other value that can be easily linked 
back to a specific scan and scan target?



It appears that $subdir is the variable used to manage this value, and 
$local_dir is the variable used to create the directory/mount point in 
agentless-unix.pl. (I have not looked at any of the other scripts to see if 
they are the same.)
Would it make sense to simply set $local_dir to something like the following:
$local_dir = "/tmp/OpenDLP/$scanname/$target/$subdir 



Thank You, 
Brian A. Kee

Original issue reported on code.google.com by [email protected] on 14 Feb 2014 at 7:44

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

No branches or pull requests

1 participant