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: Nessus 2.2.x vs. 2.3.0

Subject: Re: Nessus 2.2.x vs. 2.3.0
Date: Thu, 27 Jan 2005 08:31:10 +0100
* Renaud Deraison <deraison@nessus.org> [20050126 17:17]:
On Wed, Jan 26, 2005 at 10:09:14AM -0600, Jared Breland wrote:
Is there any easy way to tell what changed between releases?  Maybe a 
changelog available through the Nessus website?  Or release notes available 
through the website?

Announces for new versions will contain the list of changes. Otherwise,
you can always read nessus-core/CHANGES

The CHANGES file doesn't cover the differences between 2.2.x and
2.3.0, but cvs2cl should help here, as we always used verbose commit
messages.

On a CVS checkout of nessus-core you can create 'ChangeLog' with:
  cvs2cl -r -F trunk -F BOSS
Or to only include changes between 2.2 and 2.3:
  cvs2cl -r -F trunk -F BOSS -l '-d 20040801\<'

Thomas

-- 
Email: thomas@intevation.de
http://intevation.de/~thomas/
_______________________________________________
Nessus mailing list
Nessus@list.nessus.org
http://mail.nessus.org/mailman/listinfo/nessus

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