From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: Sebastian Andrzej Siewior <sebastian@breakpoint.cc>
Cc: "Kurt Roeckx" <kurt@roeckx.be>,
912087@bugs.debian.org,
"Package Development List for OpenSSL packages."
<pkg-openssl-devel@alioth-lists.debian.net>,
linux-kernel@vger.kernel.org,
"Bernhard Übelacker" <bernhardu@mailbox.org>,
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
Date: Wed, 31 Oct 2018 18:41:06 -0400 [thread overview]
Message-ID: <20181031224106.GD6236@thunk.org> (raw)
In-Reply-To: <6BBD7CF1-696B-4B5E-ABD8-A30C2F15E5C5@breakpoint.cc>
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" <tytso@mit.edu> 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.
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.
- Ted
next prev parent reply other threads:[~2018-10-31 22:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20181029223334.GH10011@roeckx.be>
2018-10-30 0:18 ` Bug#912087: openssh-server: Slow startup after the upgrade to 7.9p1 Sebastian Andrzej Siewior
2018-10-30 14:15 ` Theodore Y. Ts'o
2018-10-30 18:37 ` Kurt Roeckx
2018-10-30 20:51 ` Theodore Y. Ts'o
2018-10-31 11:21 ` Sebastian Andrzej Siewior
2018-10-31 22:41 ` Theodore Y. Ts'o [this message]
2018-11-01 22:18 ` Sebastian Andrzej Siewior
2018-11-01 23:50 ` Theodore Y. Ts'o
2018-11-02 0:24 ` Kurt Roeckx
2018-11-02 2:13 ` Theodore Y. Ts'o
2018-11-04 0:18 ` Sebastian Andrzej Siewior
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181031224106.GD6236@thunk.org \
--to=tytso@mit.edu \
--cc=912087-submitter@bugs.debian.org \
--cc=912087@bugs.debian.org \
--cc=bernhardu@mailbox.org \
--cc=debian-ssh@lists.debian.org \
--cc=kurt@roeckx.be \
--cc=linux-kernel@vger.kernel.org \
--cc=pkg-openssl-devel@alioth-lists.debian.net \
--cc=pkg-systemd-maintainers@lists.alioth.debian.org \
--cc=sebastian@breakpoint.cc \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).