search

Secure-Compliance-Solutions-LLC / GVM-Docker

Greenbone Vulnerability Management Docker Image with OpenVAS
https://securecompliance.gitbook.io/projects/
MIT License
247 stars 91 forks source link

scanner container credentials issue #53

Closed okoester closed 3 years ago

okoester commented 4 years ago

Describe the bug Public key is not generated when creating new scanner from securecompliance/gvm:scanner /data/ssh/key.pub is missing.

Results from docker logs:

gvmscan | +++++++++++++++++++++++++++++++++++++++++++++++++++++++ gvmscan | + Your OpenVAS Scanner container is now ready to use! + gvmscan | +++++++++++++++++++++++++++++++++++++++++++++++++++++++ gvmscan | gvmscan | ------------------------------------------------------- gvmscan | Scanner id: ---id removed --- gvmscan | cat: /data/ssh/key.pub: No such file or directory gvmscan | Public key: gvmscan | Master host key (Check that it matches the public key from the master): gvmscan | -------------------------------------------------------

To Reproduce Steps to reproduce the behavior:

  1. Created docker-compose.yml docker-compose.yml.txt
  2. docker-compose up -d
  3. After finished start looking for public key in logs
  4. missing key.pub file as shown above

Expected behavior Find public key to copy to GVM 11 master or have command to create public key afterwards

Screenshots If applicable, add screenshots to help explain your problem.

Additional context Add any other context about the problem here.

pixelsquared commented 4 years ago

I was able to recreate this issue and I am working on a fix.