On Mittwoch, 14. Januar 2015, Alexander Gerhards wrote: > I'm still testing the w3af-daemon and I'm getting an SSL Error. From the > osp-daemon I get: > > $ ospd-w3af -L debug > 2015-01-13 15:33:06,775 ospd.ospd: INFO: Now listening on 127.0.0.1:1236 > 2015-01-13 15:34:12,746 ospd.ospd: DEBUG: New connection from > 127.0.0.1:52043 > 2015-01-13 15:34:15,293 ospd.ospd: DEBUG: SSL error: The read operation > timed out > 2015-01-13 15:34:15,473 ospd.ospd: DEBUG: Connection to <ssl.SSLSocket > object at 0x28b9b18> closed > 2015-01-13 15:34:15,481 ospd.ospd: INFO: > 28007b2b-73a5-4eba-8fd8-f2eaa12bdd2b: Scan started. > 2015-01-13 15:34:15,483 ospd.ospd: INFO: localhost: Scan started. > 2015-01-13 15:34:15,489 ospd_w3af.wrapper: INFO: w3af scan using > fast_scan profile. > 2015-01-13 15:34:16,247 ospd.ospd: DEBUG: New connection from > 127.0.0.1:52045 > 2015-01-13 15:34:18,642 ospd.ospd: DEBUG: SSL error: The read operation > timed out > 2015-01-13 15:34:18,654 ospd.ospd: DEBUG: Connection to <ssl.SSLSocket > object at 0x7f72463ffaa0> closed > > Has anybody an idea what's going wrong?
Not really. The log reads like the communication happened successfully to some extend. I do see similar error messages here but any OSP operation is done successfully. Note that the whole OSP feature is very new and under heavy development. I use the omp command line tool to test the OSP scanners separately (without the OpenVAS Manager). -- Dr. Jan-Oliver Wagner | +49-541-335084-0 | http://www.greenbone.net/ Greenbone Networks GmbH, Neuer Graben 17, 49074 Osnabrück | AG Osnabrück, HR B 202460 Geschäftsführer: Lukas Grunwald, Dr. Jan-Oliver Wagner _______________________________________________ Openvas-discuss mailing list [email protected] https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss
