Add option for it get cve detail from cve.sqlite3.

[ymd38]

It is an error in go-cve-dictionary API when result of scan is many.

[kotakanbe]

Thanks for sending this PR.

Please paste the error msg when the result is many.

[ymd38]

When vuls send many request to go-cve-dictionary, it reach max file descriptor.

WARN[0949] Failed to HTTP GET. retrying in 13.143004491s seconds. err: HTTP GET error: [Get http://127.0.0.1:1323/cves/CVE-2015-4872: dial tcp 127.0.0.1:1323: socket: too many open files], url: http://127.0.0.1:1323/cves/CVE-2015-4872, resp: <nil> 
WARN[0949] Failed to HTTP GET. retrying in 18.903049056s seconds. err: HTTP GET error: [Get http://127.0.0.1:1323/cves/CVE-2015-4882: dial tcp 127.0.0.1:1323: socket: too many open files], url: http://127.0.0.1:1323/cves/CVE-2015-4882, resp: <nil> 
WARN[0951] Failed to HTTP GET. retrying in 15.777643131s seconds. err: HTTP GET error: [Get http://127.0.0.1:1323/cves/CVE-2015-4893: dial tcp 127.0.0.1:1323: socket: too many open files], url: http://127.0.0.1:1323/cves/CVE-2015-4893, resp: <nil> 
panic: send on closed channel

goroutine 1898 [running]:
github.com/future-architect/vuls/cveapi.cvedictClient.httpGet(0x4851f20, 0x15, 0xc8205cbe83, 0xd, 0xc8206f8c60, 0x28, 0xc8210dc360, 0xc8210dc3c0)

Thanks

[kotakanbe]

It's better to check open files limit of your OS to avoid too many open file error.
see #58 (comment)

---

I think it is worth to merge your PR.
If Vuls access to cve.db directly, we don't need to run go-cve-dictionary as server mode before scanning. Your option is useful in the case of vuls and go-cve-dictionary are running on same machine.

I need some time to think more.
Please keep this PR open.

Thanks :)

[ymd38]

I checked #58. But I thought this solution isn't best on same machine.
OK, I see.

Thanks

[kotakanbe]

Merged.

I made some changes.
#84

Thanks for your contribution!