Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #210969
| From | Curt <curty@free.fr> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: fix for no ssh |
| Date | 2019-07-08 10:50 +0200 |
| Message-ID | <yhxvs-4o4-15@gated-at.bofh.it> (permalink) |
| References | <yhgkV-2tQ-3@gated-at.bofh.it> <yhgEh-2Ai-1@gated-at.bofh.it> <yhiwq-3HJ-7@gated-at.bofh.it> |
| Organization | Unorganized |
On 2019-07-07, Andrei POPESCU <andreimpopescu@gmail.com> wrote: > > It sounds a lot like this issue: > https://www.debian.org/releases/buster/amd64/release-notes/ch-information.en.html#entropy-starvation Due to systemd needing entropy during boot and the kernel treating such calls as blocking when available entropy is low, the system may hang for minutes to hours until the randomness subsystem is sufficiently initialized (random: crng init done). For amd64 systems supporting the RDRAND instruction this issue is avoided by the Debian kernel using this instruction by default (CONFIG_RANDOM_TRUST_CPU). For amd64 systems with the RDRAND instruction, the euphemistically termed "issue" (hanging for minutes or hours!) is "avoided." That avoidance is wonderful news for me, as I happen to have an amd64 system myself. But does it support the RDRAND instruction? How do I find out? What do I do if it doesn't? Here the notes suffer from a maddening silence. At any rate, I case-insensitively grepped for the RDRAND flag in /proc/cpuinfo and came up with nada (this is a pretty old machine), if that is indeed how you discover whether you have the instruction or not. But now I'm uncertain whether this bug will affect me or not. https://daniel-lange.com/archives/152-Openssh-taking-minutes-to-become-available,-booting-takes-half-an-hour-...-because-your-server-waits-for-a-few-bytes-of-randomness.html https://lists.debian.org/debian-devel/2018/12/msg00184.html I guess I would not be affected because I'm not running an entropy-hungry service (or any services at all), but what a PITA to have gone on this wild goose chase to finally find that out (if true). These release-notes for Buster, as they stand, are apparently both wrong (migration of interface names) and misleading (if the entropy-starvation stanza had begun, "For those running services using the getrandom() system call..." or something, I probably wouldn't be here cluttering the forum with my bullshit). > Kind regards, Andrei
Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
fix for no ssh Gene Heskett <gheskett@shentel.net> - 2019-07-07 16:30 +0200
Re: fix for no ssh Tixy <tixy@yxit.co.uk> - 2019-07-07 16:50 +0200
Re: fix for no ssh Andrei POPESCU <andreimpopescu@gmail.com> - 2019-07-07 18:50 +0200
Re: fix for no ssh Nicholas Geovanis <nickgeovanis@gmail.com> - 2019-07-07 19:50 +0200
Re: fix for no ssh Andrei POPESCU <andreimpopescu@gmail.com> - 2019-07-08 09:00 +0200
Re: fix for no ssh Curt <curty@free.fr> - 2019-07-08 11:10 +0200
Re: fix for no ssh Andrei POPESCU <andreimpopescu@gmail.com> - 2019-07-08 12:20 +0200
Re: fix for no ssh Curt <curty@free.fr> - 2019-07-08 13:00 +0200
Re: fix for no ssh Curt <curty@free.fr> - 2019-07-08 16:50 +0200
Re: fix for no ssh Greg Wooledge <wooledg@eeg.ccf.org> - 2019-07-08 17:40 +0200
Re: fix for no ssh Curt <curty@free.fr> - 2019-07-08 18:20 +0200
Re: fix for no ssh Andy Smith <andy@strugglers.net> - 2019-07-08 18:50 +0200
Re: fix for no ssh Curt <curty@free.fr> - 2019-07-09 10:20 +0200
Re: fix for no ssh Andy Smith <andy@strugglers.net> - 2019-07-10 10:20 +0200
Re: fix for no ssh Curt <curty@free.fr> - 2019-07-10 11:30 +0200
Re: fix for no ssh Andy Smith <andy@strugglers.net> - 2019-07-10 13:50 +0200
Re: fix for no ssh Reco <recoverym4n@enotuniq.net> - 2019-07-10 14:30 +0200
Re: fix for no ssh Greg Wooledge <wooledg@eeg.ccf.org> - 2019-07-10 15:10 +0200
Re: fix for no ssh Curt <curty@free.fr> - 2019-07-10 16:10 +0200
Re: fix for no ssh Andy Smith <andy@strugglers.net> - 2019-07-11 14:10 +0200
Re: fix for no ssh Reco <recoverym4n@enotuniq.net> - 2019-07-11 16:20 +0200
Re: fix for no ssh Andy Smith <andy@strugglers.net> - 2019-07-11 17:10 +0200
Re: fix for no ssh Reco <recoverym4n@enotuniq.net> - 2019-07-11 17:20 +0200
Re: fix for no ssh Curt <curty@free.fr> - 2019-07-10 16:00 +0200
Re: fix for no ssh David Wright <deblis@lionunicorn.co.uk> - 2019-07-10 21:20 +0200
Re: fix for no ssh Andrei POPESCU <andreimpopescu@gmail.com> - 2019-07-10 21:30 +0200
[OT] Trustfulness. Was: Re: fix for no ssh "Thomas Schmitt" <scdbackup@gmx.net> - 2019-07-08 18:00 +0200
Re: [OT] Trustfulness. Was: Re: fix for no ssh Reco <recoverym4n@enotuniq.net> - 2019-07-08 18:10 +0200
Re: fix for no ssh Andy Smith <andy@strugglers.net> - 2019-07-08 18:10 +0200
Re: fix for no ssh Henrique de Moraes Holschuh <hmh@debian.org> - 2019-07-09 01:30 +0200
Re: fix for no ssh Curt <curty@free.fr> - 2019-07-08 10:50 +0200
Re: fix for no ssh Andrei POPESCU <andreimpopescu@gmail.com> - 2019-07-08 11:00 +0200
Re: fix for no ssh Curt <curty@free.fr> - 2019-07-08 11:20 +0200
Re: fix for no ssh Andrei POPESCU <andreimpopescu@gmail.com> - 2019-07-08 11:30 +0200
Re: fix for no ssh Curt <curty@free.fr> - 2019-07-08 11:50 +0200
Re: fix for no ssh Andrei POPESCU <andreimpopescu@gmail.com> - 2019-07-08 12:00 +0200
Re: fix for no ssh Curt <curty@free.fr> - 2019-07-08 12:30 +0200
Re: fix for no ssh Andrei POPESCU <andreimpopescu@gmail.com> - 2019-07-08 18:30 +0200
Re: fix for no ssh Curt <curty@free.fr> - 2019-07-08 19:50 +0200
Re: fix for no ssh Andy Smith <andy@strugglers.net> - 2019-07-08 20:20 +0200
Re: fix for no ssh Gene Heskett <gheskett@shentel.net> - 2019-07-08 21:00 +0200
Re: fix for no ssh Andy Smith <andy@strugglers.net> - 2019-07-08 22:50 +0200
Fwd: fix for no ssh Nicholas Geovanis <nickgeovanis@gmail.com> - 2019-07-08 23:50 +0200
Re: Fwd: fix for no ssh Andy Smith <andy@strugglers.net> - 2019-07-09 00:40 +0200
Re: fix for no ssh John Hasler <jhasler@newsguy.com> - 2019-07-09 01:20 +0200
Re: fix for no ssh Nicholas Geovanis <nickgeovanis@gmail.com> - 2019-07-09 01:30 +0200
Re: fix for no ssh Andrei POPESCU <andreimpopescu@gmail.com> - 2019-07-09 09:50 +0200
Re: fix for no ssh Andrei POPESCU <andreimpopescu@gmail.com> - 2019-07-08 23:00 +0200
Re: fix for no ssh Andrei POPESCU <andreimpopescu@gmail.com> - 2019-07-08 23:00 +0200
Re: fix for no ssh Curt <curty@free.fr> - 2019-07-10 09:50 +0200
Re: fix for no ssh Andrei POPESCU <andreimpopescu@gmail.com> - 2019-07-10 21:40 +0200
Re: fix for no ssh David Wright <deblis@lionunicorn.co.uk> - 2019-07-09 01:30 +0200
Re: fix for no ssh Andrei POPESCU <andreimpopescu@gmail.com> - 2019-07-09 10:00 +0200
Re: fix for no ssh David Wright <deblis@lionunicorn.co.uk> - 2019-07-10 01:20 +0200
Re: fix for no ssh Andrei POPESCU <andreimpopescu@gmail.com> - 2019-07-10 05:40 +0200
Re: fix for no ssh Gene Heskett <gheskett@shentel.net> - 2019-07-07 22:50 +0200
csiph-web