Received: by 2002:ac0:98c7:0:0:0:0:0 with SMTP id g7-v6csp1409395imd; Thu, 1 Nov 2018 15:19:14 -0700 (PDT) X-Google-Smtp-Source: AJdET5cUUzPZ+z88vO8AtVCvbqCcPV0lkwTGvV6zb7MDy9qatRsidmxxJEF/C8e/zMdtW3KCNzxK X-Received: by 2002:a63:f74f:: with SMTP id f15mr8822593pgk.190.1541110754193; Thu, 01 Nov 2018 15:19:14 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1541110754; cv=none; d=google.com; s=arc-20160816; b=RkmE7glQ8XmyOIrKNiMO7R39ELsa+lTVEQGCjPIg8U2Ig5IUxszlIgQcS3MoBo3CuF UK63ACh+z+1uPWiJR0+qdd2u/2X75KcjS3rUHBHdAZrWOxtJyP5ofNoSzcmVv+bonviD 7i6vYA8nv2nHb3BKNzi0NDAzv+CE/jN6nSQEOpsCXTpqR4a7qoUcdrRP0eNUvjhZeYl2 LAADKmuJhkMydPtoTbIGW/xyQmCr/fhuT79zAxeTadRyC46G7l1SLeXc8cIhj5VsAMqd 1dZ5gztNhIKBYxVfG+N+FODYCz8VR0bvwKPC2zZSn+OO5+YOb5WGX+wC2ctYCR8JDJkN ojmA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-transfer-encoding:content-disposition:mime-version :references:message-id:subject:to:from:date; bh=xvWJoHWKMur1aCK8mVXuSdq26Efi1sfmk6vnIS2qhlA=; b=RjAEWXQxLg8Z+QudKYw4FQIGBkC4NeGDK/K8DRMsUorVdXP6teM/sT9PfBbUqeXC1p PSd1f7PitWBNU4hBFmbFSoqRMA4MSjKcn4iqn1Wy+nN+K7BfJQttcBEFKDKZujPEVWao Cq0Fvqy1Cxix/fOX3BBDsmyr3JV6RJi1XRhM59YhCWQhJvMhkQ/rQD0N3j8ZU5+3GVCG NlsztNvuhwIAAK325reLURzviVddACvgVithFO8b/A8AcysJuNV4miW5iopJheHZvgOR alLC/x535HhHEoSo9WZpi2NeGIRbQYkIcQgmPGch7G5Chcg5DdcfrgWacAxtHHzjmtj4 K6dw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id b3-v6si21153273pgw.369.2018.11.01.15.18.59; Thu, 01 Nov 2018 15:19:14 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727759AbeKBHXL convert rfc822-to-8bit (ORCPT + 99 others); Fri, 2 Nov 2018 03:23:11 -0400 Received: from Chamillionaire.breakpoint.cc ([146.0.238.67]:51922 "EHLO Chamillionaire.breakpoint.cc" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726167AbeKBHXL (ORCPT ); Fri, 2 Nov 2018 03:23:11 -0400 Received: from bigeasy by Chamillionaire.breakpoint.cc with local (Exim 4.89) (envelope-from ) id 1gILI6-0005J2-60; Thu, 01 Nov 2018 23:18:14 +0100 Date: Thu, 1 Nov 2018 23:18:14 +0100 From: Sebastian Andrzej Siewior To: "Theodore Y. Ts'o" , Kurt Roeckx , 912087@bugs.debian.org, "Package Development List for OpenSSL packages." , linux-kernel@vger.kernel.org, Bernhard =?utf-8?Q?=C3=9Cbelacker?= , pkg-systemd-maintainers@lists.alioth.debian.org, debian-ssh@lists.debian.org, 912087-submitter@bugs.debian.org Subject: Re: Bug#912087: openssh-server: Slow startup after the upgrade to 7.9p1 Message-ID: <20181101221813.qfglqvmzk47m53yx@breakpoint.cc> References: <20181029223334.GH10011@roeckx.be> <20181030001807.7wailpm37mlinsli@breakpoint.cc> <20181030141544.GE15839@thunk.org> <20181030183723.GI10011@roeckx.be> <20181030205136.GB6236@thunk.org> <6BBD7CF1-696B-4B5E-ABD8-A30C2F15E5C5@breakpoint.cc> <20181031224106.GD6236@thunk.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8BIT In-Reply-To: <20181031224106.GD6236@thunk.org> User-Agent: NeoMutt/20180716 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2018-10-31 18:41:06 [-0400], Theodore Y. Ts'o wrote: > On Wed, Oct 31, 2018 at 11:21:59AM +0000, Sebastian Andrzej Siewior wrote: > > On October 30, 2018 8:51:36 PM UTC, "Theodore Y. Ts'o" wrote: > > > > > >So it's complicated. It's not a binary trusted/untrusted sort of > > >thing. > > > > What about RNDRESEEDCRNG? Would it be reasonable to issue it after writing the seed as part of the boot process? > > No, that's for debugging purposes only. Okay. I'm asking because it has been added to the kernel, marked stable and the man page has not been updated. So it did not look like a debugging interface :) > When there is sufficient entropy added (either through a hw_random > subsystem, or because RDRAND is trusted, or the RNDADDENTORPY ioctl), > the crng is automatically reseeded by credit_entropy_bits(). So it's > not needed to use RNDRESEEDCRNG. Okay. So you wrote what can be done for a system with HW-RNG/kvm. On bare metal with nothing fancy I have: [ 3.544985] systemd[1]: systemd 239 running in system mode. (+PAM… [ 10.363377] r8169 0000:05:00.0 eth0: link up [ 41.966375] random: crng init done which means I have to wait about half a minute until I can ssh into. And there is no way to speed it up? You did not oppose RNDADDTOENTCNT/RNDADDENTROPY but you wanted to make it configureable and not default, correct? > > - Ted Sebastian