MaineK00n

@gagg0412 Is this bug still happening? > Get "https://nvd.nist.gov/feeds/json/cve/1.1/nvdcve-1.1-recent.json.gz": dial tcp: lookup nvd.nist.gov: Temporary failure in name resolution Name resolution seems to have failed. There is probably a problem with...

> > Can't you also support this? > > what exactly do you want me to implement here? I am sorry that my English is not good enough to convey...

I think the reason is that fixed/unfixed is not taken into account from WpPackageFixStats here. https://github.com/future-architect/vuls/blob/2b7294a50454eb49b762e3825a85ee1aedea1ba2/models/vulninfos.go#L67-L86

@markmal Sorry for the delay in response. I think this error is occurring because it is not registered in known_hosts. > Unable to connect via SSH. Scan with -vvv option...

I have implemented a port scan feature in vuls. The current port scan only verifies the reachability of the server port. Your question about `--script` is an interesting one that...

Is what you are trying to say in this issue that we should explicitly write TLS secure settings? (e.g. `InsecureSkipVerify: false`) By the way, there is also an Issue/PR that...

I ran the command as a non-root user on RHEL 8.2, and it succeeded. ```console [non-root@rhel8 ~]$ cat /etc/redhat-release Red Hat Enterprise Linux release 8.2 (Ootpa) [non-root@rhel8 ~]$ dnf --nogpgcheck...

@barszpaw In my environment, if $USER and user in config.toml are different, the user in config.toml is used and your bug is not reproduced. Here are the config.toml and .ssh/config...

@barszpaw Show the Scan log with the vvv option. ```console $ vuls scan -debug -vvv ``` Or check if SSH can connect without password. ```console $ /usr/bin/ssh -F /home/vuls/.ssh/config -p...

Can you show me the results (//.json) when you run the vuls report? I can compare the Ubuntu vulnerability information about CVE-2017-13194 with the information about the packages you have...