Supported AmazonLinux for server mode

[masahiro331]

What did you implement:

Supported AmazonLinux for server mode. Content-Type "application/json" was already implemented.
I implemented Content-Type "plain / text".

Type of change

Please delete options that are not relevant.

• New feature (non-breaking change which adds functionality)
• This change requires a documentation update

How Has This Been Tested?

Test Conent-Type text/plain

$ ./vuls server -listen 0.0.0.0:5515 -to-localfile -format-json

# test amazon linux 1 
$ docker run -it --rm amazonlinux:2016.09.0.20161028  /bin/bash
$ curl -X POST -H "X-Vuls-Server-Name: local" -H "Content-Type: text/plain" -H "X-Vuls-OS-Family: amazon" -H "X-Vuls-OS-Release: 2 (Karoo)" -H "X-Vuls-Kernel-Release: 4.9.125-linuxkit" --data-binary "`rpm -qa --queryformat "%{NAME} %{EPOCHNUM} %{VERSION} %{RELEASE} %{ARCH}\n"`"  http://${HOST_IP}:5515/vuls

# test amazon linux 2 
$ docker run -it --rm amazonlinux:2.0.20190508  /bin/bash
$ curl -X POST -H "X-Vuls-Server-Name: local" -H "Content-Type: text/plain" -H "X-Vuls-OS-Family: amazon" -H "X-Vuls-OS-Release: 2016.09" -H "X-Vuls-Kernel-Release: 4.9.125-linuxkit" --data-binary "`rpm -qa --queryformat "%{NAME} %{EPOCHNUM} %{VERSION} %{RELEASE} %{ARCH}\n"`"  http://${HOST_IP}:5515/vuls

# test ec2 amazon linux2 
$ curl -X POST -H "X-Vuls-Server-Name: local" -H "Content-Type: text/plain" -H "X-Vuls-OS-Family: amazon" -H "X-Vuls-OS-Release: 2 (Karoo)" -H "X-Vuls-Kernel-Release: 4.14.121-109.96.amzn2.x86_64" --data-binary "`rpm -qa --queryformat "%{NAME} %{EPOCHNUM} %{VERSION} %{RELEASE} %{ARCH}\n"`"  http://${HOST_IP}:5515/vuls

Test Conent-Type application/json

$ ./vuls server -listen 0.0.0.0:5515 -to-localfile -format-json

$ curl -X POST -H "Content-Type: application/json" -d '{"Family": "amazon", "Release": "2 (Karoo)", "RunningKernel": {"Release": "4.14.121-109.96.amzn2.x86_64", "Version": ""}, "Packages": {"kernel": {"Name": "kernel", "Version": "4.14.114", "Release": "105.126.amzn2", "Arch": "x86_64"}, "dracut": {"Name": "dracut", "Version": "033", "Release": "535.amzn2.1.2", "Arch": "x86_64"}}}' http://localhost:5515/vuls

Test ssh mode with EC2 instance

$ ssh ec2_instance
$ cat config.toml
[servers.amazon]
host = "${INSTANCE_IP}"
port = "22"
user = "ec2-user"
keyPath = "$HOME/.ssh/test.pem"

$ ./vuls scan amazon
$ ./vuls report

// result 
[Jun 25 01:44:20]  INFO [localhost] amazon: 0 CVEs are detected with Library
[Jun 25 01:44:20]  INFO [localhost] OVAL is fresh: amazon 2 (Karoo)
[Jun 25 01:44:20]  INFO [localhost] amazon: 5 CVEs are detected with OVAL
[Jun 25 01:44:20]  INFO [localhost] amazon: 0 CVEs are detected with CPE
[Jun 25 01:44:20]  INFO [localhost] amazon: 0 CVEs are detected with GitHub Security Alerts
[Jun 25 01:44:20]  INFO [localhost] amazon: 0 unfixed CVEs are detected with gost
[Jun 25 01:44:20]  INFO [localhost] Fill CVE detailed information with CVE-DB
[Jun 25 01:44:20]  INFO [localhost] Fill exploit information with Exploit-DB
[Jun 25 01:44:20]  INFO [localhost] amazon: 0 exploits are detected
[Jun 25 01:44:20]  INFO [localhost] amazon: en: 0, ja: 0 alerts are detected
amazon (amazon2 (Karoo))
========================
Total: 5 (High:2 Medium:3 Low:0 ?:0), 5/5 Fixed, 483 installed, 7 updatable, 0 exploits, en: 0, ja: 0 alerts

+----------------+---------+------+------+----+-----+-------------------------------------------------+
|     CVE-ID     |  FIXED  | CERT | CVSS | AV | POC |                       NVD                       |
+----------------+---------+------+------+----+-----+-------------------------------------------------+
| CVE-2019-5953  |   fixed |      |  9.8 |  N |     | https://nvd.nist.gov/vuln/detail/CVE-2019-5953  |
| CVE-2016-10745 |   fixed |      |  8.6 |  N |     | https://nvd.nist.gov/vuln/detail/CVE-2016-10745 |
| CVE-2019-11477 |   fixed |      |  7.8 |  N |     | https://nvd.nist.gov/vuln/detail/CVE-2019-11477 |
| CVE-2019-11478 |   fixed |      |  7.5 |  N |     | https://nvd.nist.gov/vuln/detail/CVE-2019-11478 |
| CVE-2019-11479 |   fixed |      |  7.5 |  N |     | https://nvd.nist.gov/vuln/detail/CVE-2019-11479 |
+----------------+---------+------+------+----+-----+-------------------------------------------------+
--- 

$ ssh ec2_instance
$ rpm -qa --queryformat "%{NAME} %{EPOCHNUM} %{VERSION} %{RELEASE} %{ARCH}\n" > rpm.txt
$ exit
$ scp  ec2_instance:/rpm.txt . 
$ curl -X POST -H "X-Vuls-Server-Name: local" -H "Content-Type: text/plain" -H "X-Vuls-OS-Family: amazon" -H "X-Vuls-OS-Release: 2 (Karoo)" -H "X-Vuls-Kernel-Release: 4.14.121-109.96.amzn2.x86_64" --data-binary "`cat rpm.txt`"  http://${HOST_IP}:5515/vuls

// result [Jun 25 01:43:23]  INFO [localhost] Listening on 0.0.0.0:5515
[Jun 25 01:43:31]  INFO [localhost] local: 0 CVEs are detected with Library
[Jun 25 01:43:31]  INFO [localhost] OVAL is fresh: amazon 2 (Karoo)
[Jun 25 01:43:32]  INFO [localhost] local: 5 CVEs are detected with OVAL
[Jun 25 01:43:32]  INFO [localhost] local: 0 CVEs are detected with CPE
[Jun 25 01:43:32]  INFO [localhost] local: 0 CVEs are detected with GitHub Security Alerts
[Jun 25 01:43:32]  INFO [localhost] local: 0 unfixed CVEs are detected with gost
[Jun 25 01:43:32]  INFO [localhost] Fill CVE detailed information with CVE-DB
[Jun 25 01:43:32]  INFO [localhost] Fill exploit information with Exploit-DB
[Jun 25 01:43:32]  INFO [localhost] local: 0 exploits are detected
[Jun 25 01:43:32]  INFO [localhost] local: en: 0, ja: 0 alerts are detected

Checklist:

You don't have to satisfy all of the following.

• Write tests
• Write documentation
• Check that there aren't other open pull requests for the same issue/feature
• Format your source code by make fmt
• Pass the test by make test
• Provide verification config / commands
• Enable "Allow edits from maintainers" for this PR
• Update the messages below

Is this ready for review?: YES

[knqyf263]

Did you confirm that a result by server mode is the same as a result by SSH?

[masahiro331]

Yes. Confirmed in EC2 instance.
Updated PR comment.

[knqyf263]

Thanks!