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 Secure-Shell
[Top] [All Lists]

Re: Strange sshd message in /var/log/messages: sshd: ^[[60G

Subject: Re: Strange sshd message in /var/log/messages: sshd: ^[[60G
Date: Thu, 24 Mar 2005 00:09:56 -0300
On Wed, Mar 23, 2005 at 11:21:30AM -0600, Dan Nelson wrote:
In the last episode (Mar 23), Rafiq_Maniar@Dell.com said:
OpenSSH version: 3.1p1-14
OS: RHEL2.1
Kernel: 2.4.9-e.34enterprise

I have the following in the messages file:

Mar 22 13:41:24 x sshd: Starting sshd:
Mar 22 13:41:24 x sshd:  succeeded
Mar 22 13:41:24 x sshd: ^[[60G
Mar 22 13:41:24 x sshd: 
Mar 22 13:41:24 x rc: Starting sshd:  succeeded

It looks like some sort of terminal control character - but why it is
being logged I have no idea.

On Linux's console, ESC [ n G is a horizontal positioning sequence.  I
assume it's just part of redhat's [ OK ]/[FAILED] status output that is
getting logged to syslog for some reason.  Check to see if there is a
newer version of the initscripts rpm.

that's true is a redhat syslog entry is the OK! redhat message. if you need to 
solve this install
ssh from source :)

2. i recomend upgrade your kernel to 2.6 

 
Is it a known bug that has been fixed in a newer OpenSSH version? Or
is it a genuine log message that is just completely obscure? :)

is a simple log entry not a bug. but ...... i cant trust redhat !


-- 
      Dan Nelson
      dnelson@allantgroup.com
---end quoted text---

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