Add -pipe flag #294
Solved the problem of trying to read from STDIN and stopping on the way when running from CRON or AWS Lambda.
This commit is contained in:
		
							
								
								
									
										12
									
								
								README.md
									
									
									
									
									
								
							
							
						
						
									
										12
									
								
								README.md
									
									
									
									
									
								
							@@ -676,6 +676,7 @@ scan:
 | 
			
		||||
                [-http-proxy=http://192.168.0.1:8080]
 | 
			
		||||
                [-ask-key-password]
 | 
			
		||||
                [-debug]
 | 
			
		||||
                [-pipe]
 | 
			
		||||
 | 
			
		||||
                [SERVER]...
 | 
			
		||||
  -ask-key-password
 | 
			
		||||
@@ -690,6 +691,8 @@ scan:
 | 
			
		||||
        debug mode
 | 
			
		||||
  -http-proxy string
 | 
			
		||||
        http://proxy-url:port (default: empty)
 | 
			
		||||
  -pipe
 | 
			
		||||
        Use stdin via PIPE
 | 
			
		||||
  -results-dir string
 | 
			
		||||
        /path/to/results 
 | 
			
		||||
  -skip-broken
 | 
			
		||||
@@ -840,6 +843,7 @@ report:
 | 
			
		||||
                [-http-proxy=http://192.168.0.1:8080]
 | 
			
		||||
                [-debug]
 | 
			
		||||
                [-debug-sql]
 | 
			
		||||
                [-pipe]
 | 
			
		||||
 | 
			
		||||
                [SERVER]...
 | 
			
		||||
  -aws-profile string
 | 
			
		||||
@@ -886,6 +890,8 @@ report:
 | 
			
		||||
        Don't report the unscored CVEs
 | 
			
		||||
  -lang string
 | 
			
		||||
        [en|ja] (default "en")
 | 
			
		||||
  -pipe
 | 
			
		||||
        Use stdin via PIPE
 | 
			
		||||
  -refresh-cve
 | 
			
		||||
        Refresh CVE information in JSON file under results dir
 | 
			
		||||
  -results-dir string
 | 
			
		||||
@@ -913,6 +919,7 @@ With this sample command, it will ..
 | 
			
		||||
- Send scan results to slack
 | 
			
		||||
- Only Report CVEs that CVSS score is over 7
 | 
			
		||||
 | 
			
		||||
 | 
			
		||||
## Example: Put results in S3 bucket
 | 
			
		||||
To put results in S3 bucket, configure following settings in AWS before reporting.
 | 
			
		||||
- Create S3 bucket. see [Creating a Bucket](http://docs.aws.amazon.com/AmazonS3/latest/UG/CreatingaBucket.html)  
 | 
			
		||||
@@ -1108,6 +1115,7 @@ tui:
 | 
			
		||||
                [-results-dir=/path/to/results]
 | 
			
		||||
                [-refresh-cve]
 | 
			
		||||
                [-debug-sql]
 | 
			
		||||
                [-pipe]
 | 
			
		||||
 | 
			
		||||
  -cvedb-path string
 | 
			
		||||
        /path/to/sqlite3 (For get cve detail from cve.sqlite3) (default "/Users/kotakanbe/go/src/github.com/future-architect/vuls/cve.sqlite3")
 | 
			
		||||
@@ -1117,6 +1125,8 @@ tui:
 | 
			
		||||
        http://cve-dictionary.com:8080 or mysql connection string
 | 
			
		||||
  -debug-sql
 | 
			
		||||
        debug SQL
 | 
			
		||||
  -pipe
 | 
			
		||||
        Use stdin via PIPE
 | 
			
		||||
  -refresh-cve
 | 
			
		||||
        Refresh CVE information in JSON file under results dir
 | 
			
		||||
  -results-dir string
 | 
			
		||||
@@ -1152,7 +1162,7 @@ $ vuls tui 2016-12-30T10:34:38+09:00
 | 
			
		||||
# Display the previous scan results using peco
 | 
			
		||||
 | 
			
		||||
```
 | 
			
		||||
$ vuls history | peco | vuls tui
 | 
			
		||||
$ vuls history | peco | vuls tui -pipe
 | 
			
		||||
```
 | 
			
		||||
 | 
			
		||||
[](https://asciinema.org/a/emi7y7docxr60bq080z10t7v8)
 | 
			
		||||
 
 | 
			
		||||
		Reference in New Issue
	
	Block a user