"Geoff Galitz" <[email protected]> writes:

>> 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.
>
> I do have this combination working, but not from SVN.  I am using the
> openbuildservice packages.  3.x LSC (Local Security Checks) does seem to be
> more sensitive to DNS issues than 2.x, so it might be worth making sure your
> DNS settings are in order.

Hrm. I'm doing everything against localhost, which is in /etc/hosts, so
I assume dns should be okay, but that's as good a guess as any.

>>   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
>>
>
> These are normal and are (IIRC) actually SSH checks and not the scanner
> attempting to login to perform the LSCs.  

Ah. I traced some other things to being normal checks (the ro user, and
the rwa user) but I wasn't sure about these.

>>   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
>
>
> That doesn't look good, though.  SVN is always a gamble, perhaps you want to
> try the binary packages at:  
> http://download.opensuse.org/repositories/security:/openvas:/UNSTABLE/

I felt a little skittish around the opensuse packages. But I should try
current svn. Maybe it'll clear up that SIGSEGV.

Will report back shortly.

seph
_______________________________________________
Openvas-discuss mailing list
[email protected]
http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss

Reply via email to