openssh unix dev - Dec 2003 - OpenSSH on Solaris -fron SUN

I noticed this on DEBUG startup of Sun's SSH:

debug2: mac_init: found hmac-sha1
debug2: mac_init: found hmac-md5
debug1: sshd version Sun_SSH_1.0
debug1: Bad RSA1 key file /etc/ssh/ssh_host_rsa_key.
debug1: read SSH2 private key done: name rsa w/o comment success 1
debug1: load_private_key_autodetect: type 1 RSA
debug1: Bad RSA1 key file /etc/ssh/ssh_host_dsa_key.
debug1: read SSH2 private key done: name dsa w/o comment success 1
debug1: load_private_key_autodetect: type 2 DSA
debug1: Bind to port 22 on ::.

..I have tried to regenerate all the keys from scratch. No difference..

Odd thing, is that it all works just fine. The only time I see this error 
is under DEBUG. I have posted to the Sun mailing lists and no one replied.

Any ideas?




-- 
J.D. Bronson - "The Cisco Kid"
Aurora Health Care // Information Services // Milwaukee, WI USA
Office: 414.978.8282 // Fax: 414.328.8282 // Pager: 414.314.8282

J.D. Bronson wrote:
> I noticed this on DEBUG startup of Sun's SSH:
> 
> debug2: mac_init: found hmac-sha1
> debug2: mac_init: found hmac-md5
> debug1: sshd version Sun_SSH_1.0
> debug1: Bad RSA1 key file /etc/ssh/ssh_host_rsa_key.
> debug1: read SSH2 private key done: name rsa w/o comment success 1
I assume you're referring to the "Bad RSA1 key file" message?

Current versions of OpenSSH say "Not a RSA1 key file" but it's
just the
way sshd detects if a keyfile is for SSH v1 or v2: it tries loading is 
as a v1 key first (which generates that warning if it's a v2 key), and 
if that fails it tries it as a v2 key.

(See key_load_private() in authfile.c).

-- 
Darren Tucker (dtucker at zip.com.au)
GPG key 8FF4FA69 / D9A3 86E9 7EEE AF4B B2D4  37C9 C982 80C7 8FF4 FA69
     Good judgement comes with experience. Unfortunately, the experience
usually comes from bad judgement.