We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
[bbigras@bruno docker]$ docker exec -it vuls vuls prepare -config=conf/config.toml -ask-key-password SSH key password: * INFO[0003] Start Preparing (config: conf/config.toml) [Sep 13 18:50:15] INFO [localhost] Detecting OS... [Sep 13 18:50:15] INFO [localhost] Detecting OS of servers... [Sep 13 18:50:31] INFO [localhost] (1/1) Detected: 10-1-10-23: ubuntu 14.04 [Sep 13 18:50:31] INFO [localhost] Detecting OS of containers... [Sep 13 18:50:31] INFO [localhost] Installing... [Sep 13 18:50:31] INFO [10-1-10-23] apt-get update... [Sep 13 19:00:31] ERROR [localhost] Failed: Timed out: [10-1-10-23]
The text was updated successfully, but these errors were encountered:
Probably, sudo setting on the target server is not enough.
Ubuntu, Debian vuls ALL=(root) NOPASSWD: /usr/bin/apt-get, /usr/bin/apt-cache
see https://github.com/future-architect/vuls#usage-configtest
I think the error message is not helpful. I added check logics about sudo settings, ssh settings to prepare subcommand. #176 #177
Please check sudo setting on the target server and try it out with latest revision of Vuls.
Sorry, something went wrong.
[Sep 14 14:24:38] INFO [localhost] Success
Yes I didn't have a line in /etc/sudoers. Thanks!
/etc/sudoers
No branches or pull requests
The text was updated successfully, but these errors were encountered: