| To: | nessus@list.nessus.org |
|---|---|
| Subject: | Fwd: Extracting Windows name from the registry |
| From: | "Philip Morris" <phlpmrrs@googlemail.com> |
| Date: | Thu, 14 Dec 2006 12:17:11 +0000 |
| Delivered-to: | sp-com-lists@consult.net |
| Delivered-to: | nessus-list1@securepoint.com |
| Delivered-to: | nessus@list.nessus.org |
| Domainkey-signature: | a=rsa-sha1; q=dns; c=nofws; s=beta; d=googlemail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=LTRqXMk+ejr2uXe60KIfg6qoUVYUeAsAOwJHNOtst4ewBR7Kz6FN3udjkZj3GPjfie7TjJ/EuIcXNF+KIR6mrwXqfUaLyaZN9p9lFyq0zaXue3HIEf8T4NzcNf6XqDzaDEJB2r/UzgTpre/CEy58eqvoATU19/yoiLVahv7QwWc= |
| In-reply-to: | <200612140351.kBE3pmIV010688@cfa0.cfa.harvard.edu> |
| List-archive: | <http://mail.nessus.org/pipermail/nessus> |
| List-help: | <mailto:nessus-request@list.nessus.org?subject=help> |
| List-id: | Discussion of Nessus software <nessus.list.nessus.org> |
| List-post: | <mailto:nessus@list.nessus.org> |
| List-subscribe: | <http://mail.nessus.org/mailman/listinfo/nessus>, <mailto:nessus-request@list.nessus.org?subject=subscribe> |
| List-unsubscribe: | <http://mail.nessus.org/mailman/listinfo/nessus>, <mailto:nessus-request@list.nessus.org?subject=unsubscribe> |
| References: | <ab4873e10612130808i2e6d25bch2243de846dc70838@mail.gmail.com> <200612140351.kBE3pmIV010688@cfa0.cfa.harvard.edu> |
| Sender: | nessus-bounces@list.nessus.org |
|
Thnx Bob - the build.exe did it for me. Now that I have run this I now have to sort out my programming syntaxes - .... groan. All this just to suck out a value from the Windows registry. Mind you, once I have learnt how to do this I can see this plugin being invaluable. Phil ---------- Forwarded message ---------- From: Bob Babcock <rbabcock@cfa.harvard.edu> Date: 14-Dec-2006 03:51 Subject: Re: Extracting Windows name from the registry To: phlpmrrs@googlemail.com Cc: nessus@list.nessus.org > Our set up is Nesus 3.0.4 running on a Windows 2000 SP4 machine. > > I have created an .nasl file and copied it > into my plugins\scripts directory which contains all the other .nasl files. > Nessus has been restarted and yet this plugin does not appear under any of > the "Families" even though it has been set "Windows". I found, by trial, that you have to run a program to install a new or edited script. I'm at home now and nessus is at work, but I'm pretty sure it was build.exe that did the trick. Also, when changing an existing script, I had to blow away the XML files created by build.exe before the updated version would install. This seems to be the equivalent of purging the database when downloading plugins. Again, I haven't seen any documentation for this so there might be a better way. _______________________________________________ Nessus mailing list Nessus@list.nessus.org http://mail.nessus.org/mailman/listinfo/nessus |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Need more vuln information on Nessus PluginID 15640, oskar |
|---|---|
| Next by Date: | Nessus 3.0.4, James . Wilburn |
| Previous by Thread: | Re: Extracting Windows name from the registry, Bob Babcock |
| Next by Thread: | Nessus 3.0.4, James . Wilburn |
| Indexes: | [Date] [Thread] [Top] [All Lists] |