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

load_ivil help output doesn't align nicely #491

Closed
seccubus opened this Issue Jul 3, 2017 · 1 comment

Comments

Projects
None yet
1 participant
@seccubus
Member

seccubus commented Jul 3, 2017

$ bin/load_ivil --help

Usage: load_ivil --workspace <workspace name> --scan <scan name>
                 [--scanner <scanner name>] [--scannerversion <scanner version>]
		 		  --timestamp <YYYYMMDDHHmm[ss]> [--help] [--verbose] <filename>

Arguments:
--workspace (-w) - The name of the workspace the file should be loaded into
--scan (-s)		 - The name of the scan
--scanner		 - Optional: name of the scanner used. If not provided it will be
		  		   read from the IVIL file
--scannerversion - Optional: Verison of the scanner used. If not provided it will
		  		   be read from the IVIL file
--timestamp (-t) - Optional : Time the scan ran in the format YYYYMMDDHHmm[ss]
                   Defaults to the current date and time
--noprocess		 - Just load the file into Seccubus, but don't process the status
                   This is handy for importing older data or data out of sequence
		           into Seccubus. Findings that have not been seen before will
		           get the status NEW
--allowempty	 - Allow an empty ivil file to be imported (not allowed by default)
--verbose (-v)	 - Be verbose
--help (-h)		 - Print this message
<filename>		 - Path to the file to be loaded

@seccubus seccubus added the bug label Jul 3, 2017

@seccubus

This comment has been minimized.

Member

seccubus commented Jul 28, 2017

Already fixed by #500

@seccubus seccubus closed this Jul 28, 2017

seccubus added a commit that referenced this issue Jul 28, 2017

seccubus added a commit that referenced this issue Jul 28, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment