[Openvas-discuss] Having trouble with openvas 3.0.x, ssh, and gsa
seph
seph at directionless.org
Mon Apr 12 21:47:03 CEST 2010
Continuing my attempt to get this all working. I'm mostly running stuff
from svn r7230. I got a bunch of dependancies installed, and gsa can now
create credentials.
I created the scan target user, and installed their key. But I'm still
running into some issue with scans.
It doesn't seem to be working. If I look at the openvassd logs, I see:
openvassd 1d [daemon.notice] openvassd: user om : testing 127.0.0.1 (::ffff:127.0.0.1) [22568]
openvassd 1d [daemon.notice] openvassd: SIGSEGV occured !
openvassd 1d [daemon.notice] openvassd: Process 22574 seems to have died too early
openvassd 1d [daemon.notice] openvassd: process_internal_msg for openvas_tcp_scanner.nes returned -1
openvassd 1d [daemon.notice] openvassd: shared_socket: Secret/SSH/socket is unknown
[etc]
I'm not sure what that SIGSEGV is from, but since I do have credentials
defined, I expected to not see the ssh socket errors.
If I look at the sshd logs, I see the following:
sshd 26 [auth.info] sshd[23979]: Protocol major versions differ for 127.0.0.1: SSH-2.0-OpenSSH_4.7p1 Debian-8ubuntu1.2 vs. SSH-1.33-OpenVASSSH_1.0
sshd 26 [auth.info] sshd[23981]: Protocol major versions differ for 127.0.0.1: SSH-2.0-OpenSSH_4.7p1 Debian-8ubuntu1.2 vs. SSH-1.5-OpenVASSSH_1.0
sshd 26 [auth.info] sshd[23988]: Invalid user from 127.0.0.1
sshd 26 [auth.info] sshd[23527]: Bad protocol version identification \'QUIT\' from 127.0.0.1
I thought this supported ssh v2, so I suspect something is fishy in the
ssh implementation. I started looking at that, but it looked complex.
Does anyone have this working?
seph
More information about the Openvas-discuss
mailing list