From owner-freebsd-stable Sat Oct 6 10:15:49 2001 Delivered-To: freebsd-stable@freebsd.org Received: from catastrophe.net (ictus.catastrophe.net [207.227.243.193]) by hub.freebsd.org (Postfix) with SMTP id 0A06037B408 for ; Sat, 6 Oct 2001 10:15:46 -0700 (PDT) Received: (qmail 98685 invoked by uid 1002); 6 Oct 2001 17:15:37 -0000 Date: Sat, 6 Oct 2001 12:15:37 -0500 (CDT) From: Reply-To: To: Subject: Re: ssh still wont start In-Reply-To: <20011006185725.Y1013-100000@klima.physik.uni-mainz.de> Message-ID: Organization: http://users.catastrophe.net/~eric Legal-Notice: Copyright 2001 eric@catastrophe.net. The contents of this transmission and any forementioned sections stated by eric@catastrophe.net remain property of eric@catastrophe.net. MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On or about Oct 6, 2001 at 19:02 [+0200] Hartmann, O. proclaimed: ; On our SMP systems, sshd is not willing to start! After each reboot ; I have to walk to the machine's room, log into console as root and start ; ssh manually. The log error is always the same: sshd can not create ; a RSA host key and stops working. After a reboot sshd starts fine. ; Not to avoid the question, but it bothers me that the startup scripts will automatically generate a new key. I understand the reasons why, but I'd imagine the best way to do so is to regenerate the key on boot and send an alert that the old key was missing. After all, if I don't recognize a particular fingerprint when SSH'ing in, I would never connect. And if an SSH_Host_Key disappeared, to me it would seem that something "fishy" was going on. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message