When a xml report is generated, content within the <plugins> tag is missing. 
     
 <plugins>
		<error txt="No scanners list."/>
		<error txt="No plugins list."/>
	</plugins>
	<results>

On a nessus 2.0 xml output:

<plugins>
		<plugin id="10335">
			<name>Nessus TCP scanner</name>
			<version>$Revision: 1.65 $</version>
			<family>Port scanners</family>
			<cve_id></cve_id>
			<bugtraq_id></bugtraq_id>
			<category>scanner</category>
			<risk>Unknown</risk>
			<summary>Look for open TCP ports &amp; services banners</summary>
			<copyright>(C) 2004 Michel Arboi &lt;mikhail@nessus.org&gt;</copyright>
		</plugin>
		<plugin id="10180">
			<name>Ping the remote host</name>
			<version>$Revision: 1.42 $</version>
			<family>Port scanners</family>
			<cve_id></cve_id>
			<bugtraq_id></bugtraq_id>
			<category>scanner</category>
			<risk>None</risk>
			<summary>icmp/tcp pings the remote host</summary>
			<copyright>This script is Copyright (C) 1999 Renaud Deraison</copyright>
		</plugin>

Is it possible to have this generated in the openvas outputs? I am not sure if this is a bug or a feature request.

Steps to reproduce:
Generate a scan and have the output of a xml.

Date: 2009-08-30 17:51
Sender: Sujith Mohan

This issue looks fixed in OpenVAS-Client-2.0.5.

I got it working from both GUI mode and CLI Mode.

Regards
Sujith

Date: 2009-08-10 12:41
Sender: Felix Wolfsteller

I hope this issue is fixed in current trunk (with rev. 4410).
Please test, especially if output from GUI still works as
expected.

I am not sure that always the correct NVTs and Scanners are picked
(the old code tries to fetch them from the parents context -
usually the scope). Please carefully check this fact if you are
testing, e.g. by looking at a report.xml of a report after the
containing scope changed (received new nvts etc.).

Feel free to report to the openvas-devel mailinglist or contact
me on the irc channel - i am especially happy about positive
feedback ;)

Date: 2009-07-07 09:33
Sender: Felix Wolfsteller

I am NOT able to reproduce in GUI (disconnected), but in CLI.

I guess the problem is, that the information is not in the nbe
file that is queried, but in the openvasrc.

The openvasrc is used to built contexts, but probably Context
loading from CLI is done a bit different.

Usually these two files reside in the same folder (defining a
report context).

Date: 2009-07-01 11:44
Sender: Felix Wolfsteller

This is indeed a bug.
When a report is converted from a nbe file to xml there cannot
be any information about plugins/scanners, as these are not part
of the nbe but part of the openvasrc for this context/report.

In the case of a export via the GUI or directly after execution
of a scan the information is present, though.

A rough first idea would be that in nessus/xml_output_ng.c line
430 the wrong plugins are fetched.

Date: 2009-06-13 11:40
Sender: Sujith Mohan

I also face the same problem when run it from openvas-client
GUI (plugins not connected from server) and when I run openvas-client
as CLI using the command

OpenVAS-Client -n -c /home/sshovas/centos.rc -qx 192.168.1.59
9390 user pass /home/sshovas/target -T xml 231.xml

Let me know how to fix it .... 

Thanks