Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.kernel > #60970
| From | Michael Biebl <biebl@debian.org> |
|---|---|
| Newsgroups | linux.debian.devel.release, linux.debian.kernel |
| Subject | Re: Fixing Linux getrandom() in stable |
| Date | 2018-05-10 19:40 +0200 |
| Message-ID | <vNXHP-36c-3@gated-at.bofh.it> (permalink) |
| References | <vNG4i-TU-1@gated-at.bofh.it> <vNU7f-Q4-1@gated-at.bofh.it> <vNXy9-32U-3@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
Cross-posted to 2 groups.
[Multipart message — attachments visible in raw view] - view raw
Hi Russ Am 10.05.2018 um 19:22 schrieb Russ Allbery: > Michael Biebl <biebl@debian.org> writes: >> Am 10.05.2018 um 00:46 schrieb Ben Hutchings: > >>> One of the krb5 maintainers (Benjamin Kaduk) favours option 2b, and >>> also proposed that systemd could provide a wait-for-rng-ready unit to >>> support this. > >> What exactly would such a wait-for-rng-ready service do and how would it >> solve this particular problem? > > I may be misunderstanding the nature of the issue, but I believe that a > Type=oneshot service that runs a small C program that calls getrandom() > and then exit(0) when it returns would provide a useful facility. > krb5-kdc could then just declare a dependency on that service and wouldn't > be started until randomness was available. So we'd shift the waiting for randomness-to-be-available from one service to another? I don't quite see yet, where the benefit is in that. What's better if a wait-for-rng-ready binary blocks on getrandom() instead of the krb5-kdc binary itself? We wouldn't shorten the time we have to wait this way. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
Back to linux.debian.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Fixing Linux getrandom() in stable Ben Hutchings <ben@decadent.org.uk> - 2018-05-10 00:50 +0200
Re: Fixing Linux getrandom() in stable Michael Biebl <biebl@debian.org> - 2018-05-10 15:50 +0200
Re: Fixing Linux getrandom() in stable Russ Allbery <rra@debian.org> - 2018-05-10 19:30 +0200
Re: Fixing Linux getrandom() in stable Michael Biebl <biebl@debian.org> - 2018-05-10 19:40 +0200
Re: Fixing Linux getrandom() in stable Russ Allbery <rra@debian.org> - 2018-05-10 19:50 +0200
Re: Fixing Linux getrandom() in stable Ian Campbell <ijc@debian.org> - 2018-05-10 21:20 +0200
Re: Fixing Linux getrandom() in stable Benjamin Kaduk <kaduk@mit.edu> - 2018-05-10 19:50 +0200
Re: Fixing Linux getrandom() in stable Yves-Alexis Perez <corsac@debian.org> - 2018-05-13 11:30 +0200
Re: Fixing Linux getrandom() in stable Ben Hutchings <ben@decadent.org.uk> - 2018-05-13 19:20 +0200
Re: Fixing Linux getrandom() in stable Adrian Bunk <bunk@debian.org> - 2018-05-13 22:50 +0200
Re: Fixing Linux getrandom() in stable Thorsten Glaser <tg@mirbsd.de> - 2018-05-13 23:40 +0200
Re: Fixing Linux getrandom() in stable Thorsten Glaser <tg@mirbsd.de> - 2018-05-14 03:00 +0200
Re: Fixing Linux getrandom() in stable "Theodore Y. Ts'o" <tytso@mit.edu> - 2018-05-14 03:20 +0200
Re: Fixing Linux getrandom() in stable Sam Hartman <hartmans@debian.org> - 2018-05-14 15:20 +0200
Re: Fixing Linux getrandom() in stable Ben Hutchings <ben@decadent.org.uk> - 2018-05-14 04:20 +0200
Re: Fixing Linux getrandom() in stable Adrian Bunk <bunk@debian.org> - 2018-05-22 21:50 +0200
csiph-web