seph <[email protected]> writes: >>>> 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 > > Well, I just updated everything to svn 7289, and I'm still seeing the > same issue. I'm going to try to isolate what the sigsegv is.
I created a scan config that only enables "Determine OS and list of installed packages via SSH login" (oid 1.3.6.1.4.1.25623.1.0.50282). I set it up with localhost as the target, configured with an lsc credential. Then I ran the scan. No luck getting ssh to work. The openvassd log (no sigsegv this time): openvassd: user om : attempted to gain more rights by adding accept 10.41.0.0/16 openvassd: user om starts a new scan. Target(s) : 127.0.0.2, with max_hosts = 20 and max_checks = 4 openvassd: user om : testing 127.0.0.2 (::ffff:127.0.0.2) [18157] openvassd: shared_socket: Secret/SSH/socket is unknown openvassd: process_internal_msg for gather-package-list.nasl returned -1 openvassd: Finished testing 127.0.0.2. Time : 2.32 secs openvassd: user om : test complete openvassd: Total time to scan all hosts : 2 seconds If I look at the openvassd.dump, I see: resolved to name 127.0.0.2 SSH-DEBUG: Host 127.0.0.2: no extended credentials configuration. [18171](/var/lib/openvas/plugins/remote-pwcrack-options.nasl) script_get_preference_file_location: could not get local file name from preference Passwords file : If I look at the report, it says: NVT: SSH Authorization (OID: 1.3.6.1.4.1.25623.1.0.90022) No port for an ssh connect was found open. Hence local security checks might not work. NVT: Determine OS and list of installed packages via SSH login (OID: 1.3.6.1.4.1.25623.1.0.50282) Error : Remote server does not support one of the following password authentication methods : password, keyboard-interactive. It supports : publickey I have auto_enable_dependencies set to yes in openvassd.conf, I don't think there's another setting. Do I need to specify ssh credentials in the scan config? I thought they could use the ones in the target config. But that line in the dump about no extended credentials makes me wonder. seph _______________________________________________ Openvas-discuss mailing list [email protected] http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss
