George-
Thanks for taking the time to clarify those things to me. I assumed that the NTP was Network Time Protocol given that the acronym was the same and that (at least as far as my practices are concerned) security timestamps have always been NTP (network time) based.
I say that it is mostly redhat centric because out of all the other distros I have tried, SuSE Enterprise 8 was the only other distro that failed, while Fedora Core 1 seems to work according to reports. But Fedora is not an all redhat deal as it was with ver 9 and lower (at least as I understand it.) The only difference I have been seeing with distros that work and don't work has been gcc and perl versions. But with redhat, what you see is not what you get because they do so much back porting and patching while not changing versions on the software being modified, which is annoying. As far as I understand it, Redhat has become known for adopting features that break apps.
When I 'tail -f' the nessusd.messages log, and then do a 'make test' on the Net::Nessus perl mod build directory, I see three connections occurr. When I installed nessus-2.0.10a, I ran the nessus-mkcert to make the nessus server certificates. And when I do a 'nessusd -d' I see that SSL is enabled and used for client server communication, although I am using user/pass login sequences, and not cert based sequences. Going along with what you said, this could be the problem, this raises two questions:
1) How do I turn off SSL? 2) Does this mean that if I want to use SSL I can't use the perl modules?
As for the debugger, I ran it with the flags you suggested and I have not been able to figure much out, although I plan to do it again sometime this week. Running that is quite time consuming.
Nick
_______________________________________________ Nessus mailing list [EMAIL PROTECTED] http://mail.nessus.org/mailman/listinfo/nessus
