From: Jeremy Fitzhardinge <jeremy@goop.org>
To: "Heusden, Folkert van" <f.v.heusden@ftr.nl>
Cc: Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] FW: proposal for systems that do not require security
Date: Fri, 20 Apr 2001 02:02:25 -0700 [thread overview]
Message-ID: <20010420020225.G8578@goop.org> (raw)
In-Reply-To: <27525795B28BD311B28D00500481B7601F11A6@ftrs1.intranet.ftr.nl>
In-Reply-To: <27525795B28BD311B28D00500481B7601F11A6@ftrs1.intranet.ftr.nl>; from f.v.heusden@ftr.nl on Tue, Apr 10, 2001 at 02:35:52PM +0200
On Tue, Apr 10, 2001 at 02:35:52PM +0200, Heusden, Folkert van wrote:
> So, I was wondering: isn't it a nice idea to have a switch in the
> configuration menu to disable entropy-gathering in the interrupt-routines,
> have some simplistic routine (like x'=(x * m + a) % p) which returns a non-
> cryptographic value, and something similar symplistic for the network-
> traffic routines?
No, that's a very bad idea. If you think it's a problem, just remove
the random driver altogether. It's much better for something to get
ENXIO rather than thinking it's getting real randomness.
You can still get TCP sequence numbers by sampling the cycle counter or
something.
J
next prev parent reply other threads:[~2001-04-20 9:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-10 12:35 [RFC] FW: proposal for systems that do not require security Heusden, Folkert van
2001-04-10 13:11 ` Andrey Panin
2001-04-10 14:28 ` sama
2001-04-20 9:02 ` Jeremy Fitzhardinge [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-04-10 13:16 Heusden, Folkert van
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=20010420020225.G8578@goop.org \
--to=jeremy@goop.org \
--cc=f.v.heusden@ftr.nl \
--cc=linux-kernel@vger.kernel.org \
/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