Garbage in syslog
Matthew Melvin
matthewm at webcentral.com.au
Wed Dec 13 18:14:48 EST 2000
On Tue, 12 Dec 2000, Jason Stone wrote:
>
> I recently had some weirdness that maybe someone can help explain. I have
> a linux box (2.2.18pre21+ext3+freeswan) running openssh 2.2.0p and openssl
> 0.9.5a. My box crashed mysteriously and then when it started back up, I
> saw this in the logs:
>
> Dec 12 21:45:19 moonchild sshd: Starting sshd:
> Dec 12 21:45:20 moonchild sshd[509]: Server listening on 0.0.0.0 port 22.
> Dec 12 21:45:20 moonchild sshd[509]: Generating 1152 bit RSA key.
> Dec 12 21:45:20 moonchild sshd: sshd startup succeeded
> Dec 12 21:45:20 moonchild sshd: ^[[300C^[[20D
> Dec 12 21:45:20 moonchild sshd: [
> Dec 12 21:45:20 moonchild sshd: ^[[1;32mOK
> Dec 12 21:45:20 moonchild sshd: ^[[0;39m
> Dec 12 21:45:20 moonchild sshd: ]
> Dec 12 21:45:20 moonchild sshd:
>
> Whenever I see garbage characters in logs, I start to get paranoid about
> buffer overruns - so does anyone know why sshd might produce the above?
>
I don't know how it got into your syslog but this is Red Hat (or similar)'s
green 'OK' message.
Starting sshd: [ OK ]
.. obviously in the syslog these escape characters are written as litterals.
M.
--
WebCentral Pty Ltd Australia's #1 Internet Web Hosting Company
Level 1, 96 Lytton Road. Network Operations - Systems Engineer
PO Box 4169, East Brisbane. phone: +61 7 3249 2583
Queensland, Australia. pgp key id: 0x900E515F
More information about the openssh-unix-dev
mailing list