From mboxrd@z Thu Jan 1 00:00:00 1970 From: Leo Famulari Subject: bug#34580: Service ssh-daemon could not be started Date: Wed, 20 Feb 2019 18:56:34 -0500 Message-ID: <20190220235634.GA28504@jasmine.lan> References: <20190219212126.GA2371@jurong> <20190220222158.GA24808@jasmine.lan> <20190220224802.GA13647@jurong> <20190220225154.GA26281@jasmine.lan> <20190220230807.GA13841@jurong> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="qMm9M+Fa2AknHoGS" Return-path: Received: from eggs.gnu.org ([209.51.188.92]:50155) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gwbjc-0001P7-2k for bug-guix@gnu.org; Wed, 20 Feb 2019 18:57:04 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gwbjb-0001Fb-9O for bug-guix@gnu.org; Wed, 20 Feb 2019 18:57:04 -0500 Received: from debbugs.gnu.org ([209.51.188.43]:58003) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gwbja-0001FB-84 for bug-guix@gnu.org; Wed, 20 Feb 2019 18:57:03 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1gwbja-0004Rd-1W for bug-guix@gnu.org; Wed, 20 Feb 2019 18:57:02 -0500 Sender: "Debbugs-submit" Resent-Message-ID: Content-Disposition: inline In-Reply-To: <20190220230807.GA13841@jurong> List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: Andreas Enge Cc: 34580@debbugs.gnu.org --qMm9M+Fa2AknHoGS Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Thu, Feb 21, 2019 at 12:08:07AM +0100, Andreas Enge wrote: > It looks as if ssh-keygen takes too long; this is called from > openssh-activation in services/ssh.scm, with a comment > "Generate missing host keys". Are these regenerated at each boot? > If yes, is there a race condition, one action not waiting for the > previous one to finish? The host keys should not be regenerated on each boot. Wouldn't we notice if they were, since our SSH clients would complain about them having changed? --qMm9M+Fa2AknHoGS Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEsFFZSPHn08G5gDigJkb6MLrKfwgFAlxt6S8ACgkQJkb6MLrK fwhl/BAAkKQl6qI9DnmxXsA/4J16ZMiH3EEg/yG63V6X2B52sy1KU9kRV4X3P3ZV OlMwUSchSri1KXwa5EzZtBsRhCs6YJrae13hidtIlTOVtCIWeywejuiKUbDT1BTr hBpWLQFeNvk8Vmnuot/MyiHMx+7v2dn9K7LV5w/YWu92XZQIkQBh0eWeGWFDOGkn MGFkt9iEk7XPLEwoyAa82r4Gl4XjKSUye6hUkJU/qh0fwLGXMiL77P9In1pIeARk k0vh47rTeIsOM0dTXDqePF0S3pCM/zDcNLiKgYFsvVePXNSpXQO9qck5gds/P9mt MxOZ/ogd4tAhpIP2igFu8SqPflG9HWB44c4vUEgiBYA7bGxXcyB8EhVGDrJH/8gm iyP6ple0k4+wWfb2kW2YeemmMyKyG36T3AeO85P1jkkDDkzBpSmlAK05kQzrdU12 h1CzBYse0+rg0RrC0aMuKLP6WtG6UjAOMFPY+tbXV71iZdeE1vg/ncoJfd3lKX0q r1U5vdsejEks2bhjBQjKGJTuiUHuz+xgvT9OC06EzX1JP9atKAHyXIUD6H0ZEn1u eKqjWf4/nAGp6Sp2mv1lvRTz2E9+jTNTV5BuboRDbVt4NbPQRs559Aotn5cEaTMh xPI4bkVDJXEV1GZFfqGFpagmpBUCYg9X/A2paubFlKUTxkAeMDc= =vu2t -----END PGP SIGNATURE----- --qMm9M+Fa2AknHoGS--