On Wed, Apr 24, 2002 at 04:09:30PM -0500, Boutwell, George wrote:
> Wrong or right. It seems a lot like the folks with the 'old' client where hung
> out to dry, and left there with nothing else.
The thing is that we are not developping a solution to make a perfect
VPN, we develop a security scanner. So the protection communication layer
between the client and the server should not take 99% of our efforts, or
there would be something bloated|wrong here.
Now, people with old servers running around are not left in the cold
either. If you absolutely want to use the Unix client, you can have two
installations on the same host. Here's a q&d how-to :
HOW TO HAVE TWO INSTALLATIONS OF NESSUS ON THE SAME DISK
To have two installations of Nessus on the same disk, you will need
to install them at different locations. I suggest you install
Nessus 1.0.x under /usr/local/nessus-10 and Nessus 1.2.x under
/usr/local/nessus-12. To do that and _not_ be bored with shared libraries
conflicts, do the following :
- Download Nessus 1.0.x
- in your shell, type :
export LD_RUN_PATH=/usr/local/nessus-10/lib
- In each archive, do :
./configure --prefix=/usr/local/nessus-10
make
make install
- Download Nessus 1.2.x
- in your shell, type :
export LD_RUN_PATH=/usr/local/nessus-12/lib
- In each archive, do :
./configure --prefix=/usr/local/nessus-12
make
make install
- When it's done, do :
ln -s /usr/local/nessus-10/bin/nessus /usr/local/bin/nessus10
ln -s /usr/local/nessus-12/bin/nessus /usr/local/bin/nessus12
When you want to connect to an old server, type "nessus10", when you
want to connect to a newer server, type "nessus12". The trick with
LD_RUN_PATH is that the path to the proper shared libraries is hardcoded
in the elf binary produced by gcc. Hence you won't mix libnessus 1.0 and
1.2 on your installation.
Note that the nessus-installer.sh shell archive _does_ set LD_RUN_PATH
at compilation time, so this makes this setup even easier - just make
sure you install Nessus 1.0 and 1.2 under two different prefixes.
-- Renaud
