Re: Root for local check

Bonleu, Julien dijo:
> I tried to connect directly to the host with the same user I use for
> Nessus and I get all the information regarding the different package
> installed with dpkg -l.
>
> But when I try to use the same user with Nessus, the report contains
> only the “scanned” information. When I give Nessus a root account to
> log on, the report contain all the information about the packages. So
> I don’t understand why!!

This all sounds like an environment issue. When you log in with a user 
some of the ~/.bash_profile, ~/.bashrc or similar are sourced and you 
get a proper PATH defined. However, when Nessus logs in (without using a 
shell, but just using direct commands through SSH) the PATH is not well 
defined

> If it works locally with a non root account, it’s supposed to work in
> Nessus with the same account because it’s the same command.

Not really, if the PATH is set by shell configuration files for the user 
you are running with. Consider this (it's a Solaris system):

$ echo $PATH
/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X/bin
$ ssh -l admin localhost 'echo $PATH'
admin@localhost's password:
/usr/bin:/bin:/usr/sbin:/sbin

Using SSH with no shell is not the same as using SSH with a shell. Try 
running 'set' locally (with a shell) and remotely (through SSH) to see 
the difference.

Regards

Javier

_______________________________________________
Nessus mailing list
Nessus@list.nessus.org
http://mail.nessus.org/mailman/listinfo/nessus