When you install Nessus on a MacOS X host, be it by itself or thru the Fink infrastructure, the nessusd server IS a native compile of the standard source code, with what other goodies you might want to include (SSL, SNMP, etc.).
If you can live with the command-line client, that too will be running natively via a Terminal window. Only when you want to go GUI do you need to add an XFree86 server and appropiate window manager so you can run the standard X11 client that comes with the distribution, but all this is also running natively. The only thing missing is an Aqua port of the client, but this is merely a convenience issue, since all the functionality is already available. And yes, you can get all the necessary functionality NOW on a MacOS X machine, provided you are willing to live in a Unix world. I was able to teach an advanced networking class last semester with a TiBook, covering all necessary topics such as services deployment, server hardening, penetration testing, intrusion detection, network monitoring and performance testing, etc., with hardly any problem. I was able to run all the toys I needed (Nessus, Ethereal, Ettercap, Snort, Net-SNMP, etc., even Dug Song's fragroute !) "natively". So, start convincing your boss... :) Ben Vaughn wrote: > I would also be interested in such a page. Of course I think we all > would be most interested in a native port, and I hope sincerely that > someday soon this will happen. Then I can get a Mac at my job! :-) > > -----Original Message----- > From: Juan M. Courcoul [mailto:[EMAIL PROTECTED]] > > FYI, Nessus 1.2.1 has been available thru Fink via CVS for the past 24 > hours so us fink-lovers ARE up to date ! :) This time it only took 8 > days for syncronization; naturally, you will want to do a > 'nessus-update-plugins' ASAP after you've upgraded. > > ja wrote: > > >>There is obviously a lot of interest in nessus from people who use Mac >> > >>OS X. I think that someone who has it working should set up a small >>page that is sort of a specific Mac FAQ that details any compile >>errors that may be experienced in each new release. Fink obviously >>lags behind the newest versions, and thus it would be nice to have a >>place to go incase it doesn't always compile strait away.
