I had this exact same problem yesterday.
As it turns out, I have another box with the same version of OS running on
it (I have a bunch actually). I used one of those and installed to
/tmp/nessus-install. Then I did a find to list all the files there and
pumped it into a file. Then I rebuilt in /usr/local/ and used the list of
files generated to feed tar so that it would know which files to pick up. I
tarred up the results and mved it over to the other machine and untarred.
You can¹t just used the version in /tmp/nessus-install because paths get
coded in during compile
On 9/7/05 3:09 AM, "Ian Castle" <ian.castle@coldcomfortfarm.net> wrote:
On Wednesday 07 September 2005 10:37, Richard Moore wrote:
Ian Castle wrote:
Can I build it on one machine and install the binaries on another? But
then I haven't installed it from something directly from nessus.org...
Why not mount the compiler etc. via nfs?
I'll cope - I was really trying to understand the implications of the licence
- I'm quite happy with compiling from a "pristine" nessus.org source (as
opposed to a GPL version from a linux distro)... if I can have one "build"
machine and one "Production" machine. And I want to see if the licence allows
that... it is a bit ambiguous ;-).
Situation
-------------
- Build on my work station.
- Install nessus scanner on my firewall.
- Test my web server from the firewall across the network.
I want to run nessus on the firewall, so that I can test my web server
_before_ I open up the firewall to allow the world access to it.
And it is a lot quicker to scan it locally than over the network.
I expect I'll just put another box behind the firewall that can run nessus.
But that means finding another box...
Thanks for the suggestion though,
Ian.
Rich.
_______________________________________________
Nessus mailing list
Nessus@list.nessus.org
http://mail.nessus.org/mailman/listinfo/nessus
_______________________________________________
Nessus mailing list
Nessus@list.nessus.org
http://mail.nessus.org/mailman/listinfo/nessus
