not that it's much of a help, but that appears to be the code for
SSH_MSG_CHANNEL_EXTENDED_DATA according to the SSH spec You mentioned that they are Solaris machines, uniformly. Are they all the same version of ssh? all the same version of solaris? On 12/18/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Hello, I have a problem when scanning Sun Solaris. Some of them will generate the following problem: ========================================================================== It was possible to log into the remote host using the supplied password However the execution of the command "uname -a" failed, so local security checks have not been enabled Nessus returns the following error message : Nessus failed to open a new SSH channel. Receive code was not SSH_MSG_CHANNEL_OPEN_CONFIRMATION (91). It was : 95 ========================================================================== I do not understand the problem because I can log into this systems with putty or other SSH-clients without any errors. More than one SSH-session works. I have seen that someone else had the same question on July-2006, but he gets no answer. Sven -- "Ein Herz für Kinder" - Ihre Spende hilft! Aktion: www.deutschlandsegelt.de Unser Dankeschön: Ihr Name auf dem Segel der 1. deutschen America's Cup-Yacht! _______________________________________________ Nessus mailing list [email protected] http://mail.nessus.org/mailman/listinfo/nessus
-- Doug Nordwall Unix, Network, and Security Administrator Noise proves nothing. Often a hen who has merely laid an egg cackles as if she laid an asteroid. -- Mark Twain
_______________________________________________ Nessus mailing list [email protected] http://mail.nessus.org/mailman/listinfo/nessus
