Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security Focus-Sun
[Top] [All Lists]

RE: [ID 800047 auth.crit] fatal: monitor_read: unsupported request: 24

Subject: RE: [ID 800047 auth.crit] fatal: monitor_read: unsupported request: 24
Date: Fri, 13 Aug 2004 07:43:15 -0700
Try some debugging -- I'm used to ssh.com/f-secure SSH but I'm sure the 
following could be adapted:

First run the client ssh in debugging mode (-d X where X is a number 1-9).

If that doesn't give anything useful, then run an SSH daemon in debugging mode 
on a slightly different port.  For the SSH I've used this is just a -p XX 
command line switch for the port and a -d X for debugging.  Next connect to 
this special daemon and see what happens (you'll have to accept a new host key 
because of the port change).

Generally the output of the server in debug mode will give me a pretty good 
idea of why a connection is being dropped.

Best of luck,
 - Mike Myers, Mike.Myers <at> nwdc.net


-----Original Message-----
From: karthik dhayalan [mailto:karthikeyan.gemini@wipro.com]
Sent: Thursday, August 12, 2004 9:29 PM
To: focus-sun@securityfocus.com
Subject: [ID 800047 auth.crit] fatal: monitor_read: unsupported request: 24

hi guys,
       I get the above mentioned error when i try to ssh to my solaris box(SUN 
ULTRA 60)..
       what could be the exact reason??

I think its authenticating; but immediately closing...



<Prev in Thread] Current Thread [Next in Thread>