On Wed, 21 Jun 2017 11:50:18 +0100 Dario Teixeira <[email protected]> wrote:
> Hi, > > > You're trying to use the manager protocol, which is used by the > > openvasmd not openvassd. Communicating with openvassd directly (over > > OTP) is for internal usage and is not recommended for external > > clients as it may change at any time. > > Thanks for the reply. I'm trying to communicate directly with > Openvassd using the OSP protocol (formerly known as OTP, if I > understand correctly). > According to the docs [1], "<get_version/>" is part of the OSP API, > which > is why I'm puzzled it doesn't work. OSP is not the same as OTP. OSP is meant to replace OTP in some kind of future, but the current openvassd does only talk OTP as Hani said. If you're looking for scanners that can talk the 'OSP' protocol, you can find various example under the trunk/osp-servers directory in svn: https://wald.intevation.org/scm/viewvc.php/trunk/osp-servers/?root=openvas At the moment, none of them is able to process nasl code. Regards, Ben. > Note that I'm writing a daemon > that replaces Openvasmd, which is why using OMP or relying on > Openvasmd is not > an option. > > Best regards, > Dario Teixeira > > [1] http://docs.greenbone.net/API/OSP/osp-1.0.html > > _______________________________________________ > Openvas-discuss mailing list > [email protected] > https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss
pgpVttCA5rmlK.pgp
Description: OpenPGP digital signature
_______________________________________________ Openvas-discuss mailing list [email protected] https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss
