Login
[x]
Log in using an account from:
Fedora Account System
Red Hat Associate
Red Hat Customer
Or login using a Red Hat Bugzilla account
Forgot Password
Login:
Hide Forgot
Create an Account
Red Hat Bugzilla – Attachment 1458938 Details for
Bug 1572944
4.16.4-200.fc27.x86_64 takes minutes to finish crng init on some systems
[?]
New
Simple Search
Advanced Search
My Links
Browse
Requests
Reports
Current State
Search
Tabular reports
Graphical reports
Duplicates
Other Reports
User Changes
Plotly Reports
Bug Status
Bug Severity
Non-Defaults
|
Product Dashboard
Help
Page Help!
Bug Writing Guidelines
What's new
Browser Support Policy
5.0.4.rh83 Release notes
FAQ
Guides index
User guide
Web Services
Contact
Legal
This site requires JavaScript to be enabled to function correctly, please enable it.
[patch]
Proposed kernel patch if you really must use Jitter entropy
0001-random-mix-rdrand-with-entropy-sent-in-from-userspac.patch (text/plain), 2.11 KB, created by
Theodore Tso
on 2018-07-15 04:18:06 UTC
(
hide
)
Description:
Proposed kernel patch if you really must use Jitter entropy
Filename:
MIME Type:
Creator:
Theodore Tso
Created:
2018-07-15 04:18:06 UTC
Size:
2.11 KB
patch
obsolete
>From 9dee3a5a80d450dc6a63da6e6bf9ad579cb649a1 Mon Sep 17 00:00:00 2001 >From: Theodore Ts'o <tytso@mit.edu> >Date: Sat, 14 Jul 2018 23:55:57 -0400 >Subject: [PATCH] random: mix rdrand with entropy sent in from userspace > >Fedora has integrated the jitter entropy daemon to work around slow >boot problems, especially on VM's that don't support virtio-rng: > > https://bugzilla.redhat.com/show_bug.cgi?id=1572944 > >It's understandable why they did this, but the Jitter entropy daemon >works fundamentally on the principle: "the CPU microarchitecture is >**so** complicated and we can't figure it out, so it *must* be >random". Yes, it uses statistical tests to "prove" it is secure, but >AES_ENCRYPT(NSA_KEY, COUNTER++) will also pass statistical tests with >flying colors. > >So if RDRAND is available, mix it into entropy submitted from >userspace. It can't hurt, and if you believe the NSA has backdoored >RDRAND, then they probably have enough details about the Intel >microarchitecture that they can reverse engineer how the Jitter >entropy daemon affects the microarchitecture, and attack its output >stream. And if RDRAND is in fact an honest DRNG, it will immeasurably >improve on what the Jitter entropy daemon might produce. > >This also provides some protection against someone who is able to read >or set the entropy seed file. > >Signed-off-by: Theodore Ts'o <tytso@mit.edu> >Cc: stable@vger.kernel.org >--- > drivers/char/random.c | 10 +++++++++- > 1 file changed, 9 insertions(+), 1 deletion(-) > >diff --git a/drivers/char/random.c b/drivers/char/random.c >index 0706646b018d..283fe390e878 100644 >--- a/drivers/char/random.c >+++ b/drivers/char/random.c >@@ -1896,14 +1896,22 @@ static int > write_pool(struct entropy_store *r, const char __user *buffer, size_t count) > { > size_t bytes; >- __u32 buf[16]; >+ __u32 t, buf[16]; > const char __user *p = buffer; > > while (count > 0) { >+ int b, i = 0; >+ > bytes = min(count, sizeof(buf)); > if (copy_from_user(&buf, p, bytes)) > return -EFAULT; > >+ for (b = bytes ; b > 0 ; b -= sizeof(__u32), i++) { >+ if (arch_get_random_int(&t)) >+ continue; >+ buf[i] ^= t; >+ } >+ > count -= bytes; > p += bytes; > >-- >2.18.0.rc0 >
You cannot view the attachment while viewing its details because your browser does not support IFRAMEs.
View the attachment on a separate page
.
View Attachment As Diff
View Attachment As Raw
Actions:
View
|
Diff
Attachments on
bug 1572944
: 1458938