Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security Nessus-Users
[Top] [All Lists]

Re: NessusClient 1.0.0.RC1

Subject: Re: NessusClient 1.0.0.RC1
Date: Fri, 28 Oct 2005 12:30:58 +0200
Jan-Oliver Wagner wrote:

On Mon, Oct 24, 2005 at 02:00:40PM +0200, Javier Fernandez-Sanguino wrote:

1- It would be nice if it integrated with GNOME/KDE menus by registering itself as an application (see http://www.freedesktop.org/wiki/Standards_2fdesktop_2dentry_2dspec)
I do this in the Debian packages, so that users don't have to do it manually (or using Smeg: http://www.realistanew.com/projects/smeg/)


does it mean that we can use the files you created and add them
to the NessusClient package?

Sure, but the files I created are:

1.- a menu file (Debian-specific, it generates entries for both GNOME and KDE under a "Debian" menu)
2.- an xpm file (provided by a Debian user) for the logo


Whileas freedesktop definitions use a different format and can use the png format.

6.- It would be nice if the TeX file generated from LyX was distributed with the source package, that way packagers could use it to generate the ps/html versions. Notice that there is no way to "automatically" have LyX reconfigure itself from the command line (in order to retrieve TeX formats installed) so it is not easy to have that compiled automatically and distributed with binary packages (either with the client or as a separate 'nessusclient-doc' package)


hm, not sure whether I understand you here.
E.g. with "lyx -e latex users-manual.lyx" you can create
a latex file easily.

I can only do that if I first startup LyX (after installing it) and, from the GUI, regenerate the refernces to TeX files. That _cannot_ be done by automatic binary package builders and requires starting up a GUI (there's no CLI option for LyX to do that). Having the TeX format there makes it much easier to build, since it will work just as soon as you install TeTeX and the relevant classes. My concern is that the current Makefile is not something that you can execute by doing:


0- install TeTeX
1- install LyX
2- compile

Which can be automated, but rather:

0- install TeTex
1- install LyX
2- Update TeTeX classes in LyX running the GUI
3- compile

which cannot.

BTW, it's rather nice that this client has i18n support. I'll try to get around and provide a Spanish translation for it if time permits.


note, that it is not the full automized routines like
the autotools usually provide.

Understood.

I have Debian packages ready, still have to test them, though, but will send an e-mail to the list once they are (semi-ready)


I am looking forward to them ... :-)

All are up now at http://people.debian.org/~jfs/nessus/client


The packages are built, but I have not tested wether they work at all (i.e. wether they run properly against a server). If you can give them I try I would appreciate it. I might have some spare time this weekend to give them a try too, can you forward me the next RC?


Javier
_______________________________________________
Nessus mailing list
Nessus@list.nessus.org
http://mail.nessus.org/mailman/listinfo/nessus

<Prev in Thread] Current Thread [Next in Thread>